Terracotta Discussion Forums

Hi all,

Recently, my server has been upgraded from JDK 1.5 to JDK 1.6.
By running time by time, my server encounters errors on managing cluster. I have tired to upgrade the quartz version to 1.6.6. However, another error appears when starting the server.
"Error handling misfires: Couldn't retrieve trigger: [jcc][10150][10300][3.50.152] Invalid parameter: Unknown column name PRIORITY"

I deeply appreciate if someone can advise on it
Thanks!

Server Info.
==============================================
App server = JBOSS 4.0.3
quartz version = 1.5.2
Database server = DB2/AIX64 9.1.7
==============================================

Error:
==============================================
ERROR [JobStoreTX] ClusterManager: Error managing cluster: Failure identifying failed instances when checking-in: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=3.50.152
org.quartz.JobPersistenceException: Failure identifying failed instances when checking-in: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=3.50.152 [See nested exception: com.ibm.db2.jcc.b.pm: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=3.50.152]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.findFailedInstances(JobStoreSupport.java:2100)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.clusterCheckIn(JobStoreSupport.java:2117)
at org.quartz.impl.jdbcjobstore.JobStoreTX.doCheckin(JobStoreTX.java:1383)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:2378)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:2409)
* Nested Exception (Underlying Cause) ---------------
com.ibm.db2.jcc.b.pm: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=3.50.152
at com.ibm.db2.jcc.b.wc.a(wc.java:568)
at com.ibm.db2.jcc.b.wc.a(wc.java:57)
at com.ibm.db2.jcc.b.wc.a(wc.java:126)
at com.ibm.db2.jcc.b.jk.b(jk.java:3578)
at com.ibm.db2.jcc.t4.eb.h(eb.java:266)
at com.ibm.db2.jcc.t4.eb.a(eb.java:227)
at com.ibm.db2.jcc.t4.eb.c(eb.java:31)
at com.ibm.db2.jcc.t4.u.a(u.java:32)
at com.ibm.db2.jcc.t4.j.Xb(j.java:245)
at com.ibm.db2.jcc.b.jk.X(jk.java:3412)
at com.ibm.db2.jcc.t4.d.g(d.java:1837)
at com.ibm.db2.jcc.b.bc.a(bc.java:207)
at com.ibm.db2.jcc.b.jk.c(jk.java:296)
at com.ibm.db2.jcc.b.jk.next(jk.java:258)
at org.jboss.resource.adapter.jdbc.WrappedResultSet.next(WrappedResultSet.java:1184)
at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.selectSchedulerStateRecords(StdJDBCDelegate.java:3698)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.findFailedInstances(JobStoreSupport.java:2043)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.clusterCheckIn(JobStoreSupport.java:2117)
at org.quartz.impl.jdbcjobstore.JobStoreTX.doCheckin(JobStoreTX.java:1383)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:2378)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:2409)
==============================================

The following is the quartz.properties
==============================================
org.quartz.scheduler.instanceName = DefaultQuartzScheduler
org.quartz.scheduler.rmi.export = false
org.quartz.scheduler.rmi.proxy = false
org.quartz.scheduler.wrapJobExecutionInUserTransaction = false

org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 10
org.quartz.threadPool.threadPriority = 5
org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread = true

org.quartz.jobStore.misfireThreshold = 60000

org.quartz.jobStore.class = org.quartz.simpl.RAMJobStore
==============================================

Quartz 1.6.6 requires a "priority" column on the triggers table. Use and "alter table" SQL statement to create it, and you should be set.