Lots of errors in log file after upgrading to 3.2.1

[Remo Siegwart]

After upgrading to 3.2.1 the log file of JIRA is full of errors from the scheduler:

2015-02-18 14:12:04,017 QuartzScheduler_TSP-Quartz-Clustered-Worker-TSP-Quartz-1424265063919_ClusterManager ERROR V000503 619x301x1 1phk57p 10.80.41.22 /rest/plugins/1.0/installed-marketplace [quartz.impl.jdbcjobstore.JobStoreTX] ClusterManager: Error managing cluster: Failure obtaining db row lock: Invalid object name 'TSP_QRTZ_LOCKS'.
org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: Invalid object name 'TSP_QRTZ_LOCKS'. [See nested exception: java.sql.SQLException: Invalid object name 'TSP_QRTZ_LOCKS'.]
    at org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:109)
    at org.quartz.impl.jdbcjobstore.DBSemaphore.obtainLock(DBSemaphore.java:112)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.doCheckin(JobStoreSupport.java:3221)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:3847)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:3883)
Caused by: java.sql.SQLException: Invalid object name 'TSP_QRTZ_LOCKS'.
    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
    at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
    at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
    at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477)
    at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
    at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
    at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
    at org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:89)
    ... 4 more

We are using JIRA 6.3.12 and had to downgrade the scheduler to 3.1.3 to make the errors disappear.

[jost]

Hi Remo, we currently working on this bug. In near future we will fix this bug and release new version contains fixes.

Regards

[jost]

Hi Remo,

We just updated The Scheduler plugin. New release (3.2.2) contains fix for your bug. Please try to update it and let us know if new release is working well.

Release notes

   -Fixed an error associated with the MS SQL database.
   -Fixed a compatibility with JIRA Data Center (JIRA clustering is only available from 6.3 onwards)

Please notice that The Scheduler 3.2 and above is available for JIRA 6.3 – 6.3.15.

The Scheduler on marketplace:

https://marketplace.atlassian.com/download/plugins/pl.com.tt.jira.plugin.theschedulerpro/version/177

Additionally here you can find an official documentation:

https://bitbucket.org/apdc/the-scheduler/wiki/Home Regards