TheScheduler Plugin Failing

[Ops]

Hi All,

I have passed the below request to the vendor, but was wondering whether anyone on here could help.

We have purchased The Scheduler plugin, and have been using it for a few months without any issues. After upgrading to JIRA v6.3.15 from JIRA v6.3.10, the plugin is failing to fire our scheduled issues.

The JIRA logs are showing the below at the time the tasks should have been created:

2015-02-23 01:00:03,728 QuartzScheduler_TSP-Quartz-Clustered-Worker-TSP-Quartz-1424639989847_ClusterManager ERROR matthew.omalley 1275x238x2 yig15o 192.168.60.187 /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:372)

     at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)

     at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)

     at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671)

     at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:505)

     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

2015-02-23 01:01:03,740 QuartzScheduler_TSP-Quartz-Clustered-Worker-TSP-Quartz-1424639989847_ClusterManager ERROR matthew.omalley 1275x238x2 yig15o 192.168.60.187 /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:372)

     at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2988)

     at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2421)

     at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:671)

     at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:505)

     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

Atlassian have confirmed the below:

“In our situation here, it seems that the situation that we are facing is limited to the functionalities of the add-on, and the scheduled jobs of JIRA itself is working as intended (filter subscriptions, etc).

This being the case, I have to inform you that as Atlassian does not develop, maintain or support TheScheduler add-on, I'm rather limited on what we can do on this ticket.”

Would any one be able to advise what we need to do to get this resolved?

Matthew

[Daniel Wester · Accepted solution]

Looks like there's a similar report https://bitbucket.org/apdc/the-scheduler/issue/38/lots-of-errors-in-log-file-after-upgrading . Best bet would be to reach out to the vendor.

More than likely something changed in JIRA's api in the patch level and they'll need to fix it. According to the issue though - they rolled the add-on back to 3.1.3 to fix the issue.

[Ops]

Thanks Daniel and Jacek.

I will uninstall The Scheduler, and install version 3.1.3 as suggested.

[jost]

Hi Matthew,

Daniel is right and we currently working on this bug.

Please uninstall The Scheduler and install oldest version of plugin (3.1.3).

In near future we will fix this bug and release new version contains fixes.

You can download The Scheduler 3.1.3 from:

https://marketplace.atlassian.com/plugins/pl.com.tt.jira.plugin.theschedulerpro/server/overview