2014-03-24 62 views
0

我在我的web應用程序中使用了Quartz作業。當我使用Quartz 1.6.5和Teradata數據庫版本13.10時,一切正常。石英錯誤:沒有合適的驅動程序

我在石英老版本中遇到了頻繁的死鎖問題。所以,我將我的版本升級到Quartz2.2.1。當我在Teradata數據庫版本13.10中使用Quartz 2.2.1時,一切正常。

後來我們在Teradata 13.10中遇到了一個奇怪的charset問題,所以我們升級到了Teradata 14.0。現在

,我們面臨着一個奇怪的問題,當我們用石英2.2.1和Teradata數據庫版本14.0

我們得到了以下異常,

INFO >2014-03-20 10:35:34,541 com.mchange.v2.log.MLog[main]: MLog clients using log4j logging. 
INFO >2014-03-20 10:35:35,007 com.mchange.v2.c3p0.C3P0Registry[main]: Initializing c3p0-0.9.1 [built 16-January-2007 14:46:42; debug? true; trace: 10] 
INFO >2014-03-20 10:35:35,504 com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource[main]: Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acquireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCommitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> false, checkoutTimeout -> 0, connectionCustomizerClassName -> null, connectionTesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, dataSourceName -> 30b5x8901q4ns4b1b241po|1b7bf86, debugUnreturnedConnectionStackTraces -> false, description -> null, driverClass -> com.objectriver.jdbc.driver.L2PDriver, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false, identityToken -> 30b5x8901q4ns4b1b241po|1b7bf86, idleConnectionTestPeriod -> 0, initialPoolSize -> 3, jdbcUrl -> jdbc:teradata://10.219.82.10/database=T01DGF0_Q,CHARSET=UTF8,TMODE=TERA, lastAcquisitionFailureDefaultUser -> null, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime -> 0, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 10, maxStatements -> 0, maxStatementsPerConnection -> 120, minPoolSize -> 1, numHelperThreads -> 3, numThreadsAwaitingCheckoutDefaultUser -> 0, preferredTestQuery -> null, properties -> {user=******, password=******}, propertyCycle -> 0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> false ] 
WARN >2014-03-20 10:36:04,519 com.mchange.v2.resourcepool.BasicResourcePool[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0]: [email protected]1 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: 
java.sql.SQLException: No suitable driver 
at java.sql.DriverManager.getDriver(DriverManager.java:264) 
at com.mchange.v2.c3p0.DriverManagerDataSource.driver(DriverManagerDataSource.java:224) 
at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:135) 
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) 
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) 
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) 
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) 
at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) 
at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) 
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 
INFO >2014-03-20 10:36:05,903 com.ssc.faw.common.LogManager[GenCache]: GenCache.Worker(1) created 
WARN >2014-03-20 10:36:06,657 com.mchange.v2.resourcepool.BasicResourcePool[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2]: [email protected]a -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: 
java.sql.SQLException: No suitable driver 
at java.sql.DriverManager.getDriver(DriverManager.java:264) 
at com.mchange.v2.c3p0.DriverManagerDataSource.driver(DriverManagerDataSource.java:224) 
at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:135) 
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) 
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) 
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) 
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) 
at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) 
at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) 
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 
WARN >2014-03-20 10:36:06,657 com.mchange.v2.resourcepool.BasicResourcePool[com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1]: [email protected]0 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: 
java.sql.SQLException: No suitable driver 
at java.sql.DriverManager.getDriver(DriverManager.java:264) 
at com.mchange.v2.c3p0.DriverManagerDataSource.driver(DriverManagerDataSource.java:224) 
at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:135) 
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182) 
at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:171) 
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:137) 
at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014) 
at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32) 
at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810) 
at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547) 

請查找以下石英性質和工作崗位XML ,

的quartz.properties

#============================================================== 
# Registry Scheduler Properties 
#============================================================== 
org.quartz.scheduler.instanceName=Service_Dgf_Quartz_Scheduler 
org.quartz.scheduler.makeSchedulerThreadDaemon = true 

#============================================================================ 
# Cluster Configuration 
#============================================================================ 
org.quartz.jobStore.isClustered = true 
org.quartz.jobStore.clusterCheckinInterval = 60000 
org.quartz.jobStore.selectWithLockSQL=LOCKING ROW FOR WRITE SELECT * FROM {0}LOCKS WHERE LOCK_NAME = ? 
org.quartz.scheduler.instanceId = AUTO 

#============================================================== 
# Configure ThreadPool 
#============================================================== 
org.quartz.threadPool.class=org.quartz.simpl.SimpleThreadPool 
org.quartz.threadPool.threadCount=10 
org.quartz.threadPool.threadPriority=5 

#============================================================== 
# Configure JobStore 
#============================================================== 
org.quartz.jobStore.misfireThreshold = 60000 
org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX 
org.quartz.jobStore.driverDelegateClass = com.ssc.mfw.server.quartz.TeradataDelegate 

#======================================================================================== 
# Configure JobInitializer Plugin 
#======================================================================================== 
org.quartz.plugin.jobInitializer.wrapInUserTransaction = false 
org.quartz.plugin.jobInitializer.class = org.quartz.plugins.xml.XMLSchedulingDataProcessorPlugin 
org.quartz.plugin.jobInitializer.scanInterval = 0 
org.quartz.plugin.jobInitializer.fileNames=quartz/service_dgf_jobs.xml 
org.quartz.plugin.jobInitializer.failOnFileNotFound = true 

#============================================================================ 
# Configure Plugins 
#============================================================================ 
org.quartz.plugin.triggHistory.class = org.quartz.plugins.history.LoggingJobHistoryPlugin 

#============================================================================ 
# Configure JobStore Additional Code 
#============================================================================ 
org.quartz.jobStore.useProperties = false 
org.quartz.jobStore.dataSource = QuartzDS 
org.quartz.jobStore.tablePrefix = QRTZ_ 

org.quartz.dataSource.QuartzDS.connectionProvider.class=com.ssc.mfw.server.util.TeradataConnectionProvider 

quartz_jobs.xml

<?xml version="1.0" encoding="UTF-8"?> 
<job-scheduling-data 
xmlns="http://www.quartz-scheduler.org/xml/JobSchedulingData" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.quartz-scheduler.org/xml/JobSchedulingData http://www.quartz-scheduler.org/xml/job_scheduling_data_1_8.xsd" 
version="1.8"> 

<schedule> 
<job> 
<name>simpleJob</name> 
<group>SimpleGroup</group> 
<description>Mart Creation Job</description> 
<job-class>com.ssc.mfw.server.job.VirtualMartCreationJob</job-class> 
</job> 
<trigger> 
<!-- ServiceNotification will be fired every 5 minutes --> 
<cron> 
<name>simpleJobTrigger</name> 
<job-name>simpleJob</job-name> 
<job-group>SimpleGroup</job-group> 
<cron-expression>0 0/5 * * * ?</cron-expression> 
</cron> 
</trigger> 
</schedule> 

<schedule> 
<job> 
<name>dashboardJob</name> 
<group>dashboardGroup</group> 
<description>Dashboard Job</description> 
<job-class>com.ssc.mfw.server.job.DashBoardJob</job-class> 
</job> 
<trigger> 
<!-- ServiceNotification will be fired every 12 hours --> 
<cron> 
<name>dashboardJobTrigger</name> 
<job-name>dashboardJob</job-name> 
<job-group>dashboardGroup</job-group> 
<cron-expression>0 0 0/12 * * ?</cron-expression> 
</cron> 
</trigger> 
</schedule> 

<schedule> 
<job> 
<name>updateAsAtTmsJob</name> 
<group>updateAsAtTmsGroup</group> 
<description>Update DB Key Job</description> 
<job-class>com.ssc.mfw.server.job.UpdateAsAtTmsJob</job-class> 
</job> 
<trigger> 
<!-- ServiceNotification will be fired every 4 hours --> 
<cron> 
<name>updateAsAtTmsJobTrigger</name> 
<job-name>updateAsAtTmsJob</job-name> 
<job-group>updateAsAtTmsGroup</job-group> 
<cron-expression>0 0 0/4 * * ?</cron-expression> 
</cron> 
</trigger> 
</schedule> 
</job-scheduling-data> 

我們正面臨着只有上面說的,當石英數據庫表是空的。如果石英錶包含作業細節,作業運行良好。

任何一個建議可以引起什麼問題?我在這裏做錯了什麼?

Regards, Suresh。

回答

0

您的問題非常簡單:JDBC無法將您提供的數據庫的URL解析爲相應的Driver類。您可以通過多種不同的方式很容易解決這個問題,但不幸的是,很難給出具體的建議,因爲你所有的JDBC配置的背後卻隱藏着......

org.quartz.dataSource.QuartzDS.connectionProvider.class=com.ssc.mfw.server.util.TeradataConnectionProvider 

在所有的可能性,該類都不會org.quartz.utils.PoolingConnectionProvider,當它是這樣做的,它提供String dbDriver作爲它的superconstructor的第一個參數。 (該字符串可能是硬編碼的,或者以某種方式進行外部配置。)您需要將該字符串更新爲適合您新版本Teradata的JDBC驅動程序。您還需要確保您正在使用的JDBC URL(可能是TeradataConnectionProvider的superconstructor的第二個參數)是新數據庫的URL,與您感到驚訝的dbDriver類一致。檢查驅動程序名稱和兼容的JDBC URL格式的Teradata 14 JDBC文檔文檔。

(如果你的TeradataConnectionProvider實現提供了一個Properties對象超類,確保關鍵「驅動程序」綁定到JDBC驅動程序類名和字符串URL綁定的相應的JDBC URL)。

(如果您想更具體的幫助,包括源TeradataConnectionProvider。)

(或者,更透明,配置數據源直接使用定義here的配置屬性。)

0

我們使用其他第三方罐子創建con nections。該第三方jar以特定格式接受URL。我們以錯誤的格式發送網址。現在,我們已經解決了這個問題並使其工作。 @Steve:感謝您的時間和支持。

相關問題