Problems with TheScheduler after upgrade

[ESco Operations]

Hi Support

After upgrading to JIRA 6.4.12 last night none of the issues scheduled via TheScheduler add on have fired when they were supposed to. We are running version 3.2.2 - i.e. the latest version pre JIRA 7.

The issues fire manually when I hit Fire but not when their cron schedule tells them too.

Can you let me know what information I can provide that will be off assistance to you to troubleshoot this?

Matthew

[jost]

Hello Matthew,

The newest version of The Scheduler Plugin is 3.2.14 (the last version published on Marketplace is 3.2.13) - you can download it from our server: https://bitbucket.org/apdc/the-scheduler/downloads.

Since version 3.2 TSP supports cluster version of JIRA Server. It was associated with the many complications. But we are fixed all of them. Version 3.2.13 and 3.2.14 are fully stable. Please to update The Scheduler and let us know wheater this solve your issue.

Regards,

Jacek Ostrowski

[ESco Operations]

Hello Jacek

I have downloaded and installed 3.2.14 as suggested but unfortunately I am still seeing the same issue. The fire time passes and The Scheduler misses it. The Prev Fire Time remains unchanged whereas the Next Fire Time updates as it should.

Matthew

[Sunnie Jackson]

I'm also experiencing this same problem. We upgraded to Jira 6.4.12 and are running TheScheduler 3.2.13 on a trial run.

Sunnie

[ESco Operations]

I am glad it isn't just us! Hopefully @ostrowskij gets back to us shortly.

@elasunnie - the plugin is great but the last JIRA upgrade seems to have just stopped it dead...

[Sunnie Jackson]

We had a blip but our issues are now firing as expected. I will note that knowing the universal time zone of the instance is important to scheduling the triggers. This is not modified by the project Service Desk calendar.

Sunnie

[ESco Operations]

Mine is still not working.

I see the below in the logs around the time tasks should be firing:

2016-02-02 01:00:59,888 QuartzScheduler_TSP-Quartz-Clustered-Worker-1453942461152-TSP-Quartz-1453942461152_ClusterManager ERROR [quartz.impl.jdbcjobstore.JobStoreTX] ClusterManager: Error managing cluster: Failure obtaining db row lock: No row exists in table jiraschema.TSP_QRTZ_LOCKS for lock named: STATE_ACCESS org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: No row exists in table jiraschema.TSP_QRTZ_LOCKS for lock named: STATE_ACCESS [See nested exception: java.sql.SQLException: No row exists in table jiraschema.TSP_QRTZ_LOCKS for lock named: STATE_ACCESS] 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: No row exists in table jiraschema.TSP_QRTZ_LOCKS for lock named: STATE_ACCESS at org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:91)

[ESco Operations]

Still not working and still no response from the supplier.

It looks as if my issue may be linked to issue 62 from July 2015. The TSP_QRTZ_LOCKS table was empty in my instance so I have populated this using the details supplier in the linked task. A test job has fired successfully so I am hopeful that the existing jobs will fire over night as they should.

[Ziniewicz Maciej]

Hello,

Last Firday we released new version of The Scheduler Plugin(v3.2.16). This version should resolve your problem.

New TSP is published on Atlassian Marketplace, so you can do an update by perform "Update" button on add-ons page. You can also download it from here: https://marketplace.atlassian.com/plugins/pl.com.tt.jira.plugin.theschedulerpro/versions

Please update your TSP and let us know if it helped.