Scheduler does not trigger any more

[Former user]

This issue was requested via Atlassian Answers already but I didn't recieve any reply yet:

Since a few month, out JIRA Issue scheduler does not trigger / create issues any more. Scheduler Version 3.2.6 / The problem even occurs with the newest Jira Version JIRA v6.4.8.

In case the Scheduler add on starts, tries to trigger a scheduled issue or even if I try to export existing scheduled issues, i get the exception:

2015-07-17 12:06:52,269 Thread-35 ERROR [quartz.impl.jdbcjobstore.JobStoreTX] ClusterManager: Error managing cluster: Failure obtaining db row lock: No row exists in table TSP_QRTZ_LOCKS for lock named: STATE_ACCESS org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: No row exists in table TSP_QRTZ_LOCKS for lock named: STATE_ACCESS [See nested exception: java.sql.SQLException: No row exists in table TSP_QRTZ_LOCKS for lock nam ed: 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.initialize(JobStoreSupport.java:3832) at org.quartz.impl.jdbcjobstore.JobStoreSupport.schedulerStarted(JobStoreSupport.java:639) at org.quartz.core.QuartzScheduler.start(QuartzScheduler.java:513) at org.quartz.core.QuartzScheduler$1.run(QuartzScheduler.java:536) at java.lang.Thread.run(Thread.java:745) Caused by: java.sql.SQLException: No row exists in table TSP_QRTZ_LOCKS for lock named: STATE_ACCESS at org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:91) ... 8 more

Database is mysql Server version: 5.5.43.

[jost]

Hi,

Thank you for reporting this problem. We will analyze it and let you know about the results.

Regards

[jost]

Hi,

We cannot reproduce your bug. Could you give us more information:

• Do you have any errors in log file? (Please send this file to us)?

• Could you check if the table "TSP_QRTZ_LOCKS" actually exist in your database?

Regards

[ChristianR]

This is the output in catalina.out in case a manually fire a scheduled issue:

2015-07-21 14:42:44,925 QuartzScheduler_TSP-Quartz-Clustered-Worker-TSP-Quartz-1437127550655_ClusterManager ERROR [quartz.impl.jdbcjobstore.JobStoreTX] ClusterManager: Error managing cluster: Failure obtaining db row lock: No row exi sts in table TSP_QRTZ_LOCKS for lock named: STATE_ACCESS org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: No row exists in table TSP_QRTZ_LOCKS for lock named: STATE_ACCESS [See nested exception: java.sql.SQLException: No row exists in table TSP_QRTZ_LOCKS for lock nam ed: 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 TSP_QRTZ_LOCKS for lock named: STATE_ACCESS at org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:91) ... 4 more

This is logged in access log (# = anonymized)

0:0:0:0:0:0:0:1 882x7847x1 <#user#> [21/Jul/2015:14:42:49 +0200] "GET /jira/rest/thescheduler/1.0/scheduled-issue/4/fire HTTP/1.1" 200 44 205 "https://<#server#>/jira/browse/<#project#>/?selectedTab=pl.com.tt.jira.plugin.theschedulerpro:sche duled-issues-project-tab-panel" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0" "7nalpu"

mysql> describe TSP_QRTZ_LOCKS; +------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +------------+--------------+------+-----+---------+-------+ | SCHED_NAME | varchar(120) | YES | | NULL | | | LOCK_NAME | varchar(40) | NO | | NULL | | +------------+--------------+------+-----+---------+-------+ 2 rows in set (0.00 sec)

mysql> select * from TSP_QRTZ_LOCKS; Empty set (0.00 sec)

Regards,

Christian

[jost]

Hi Christian,

For some reasons you don't have one of required row in this table TSP_QUARTZ_LOCKS.

This table should contain 5 rows:

+------------+-----------------+

| SCHED_NAME | LOCK_NAME |

+------------+-----------------+

| NULL | CALENDAR_ACCESS |

| NULL | JOB_ACCESS |

| NULL | MISFIRE_ACCESS |

| NULL | STATE_ACCESS |

| NULL | TRIGGER_ACCESS |

+------------+-----------------+

Please to add it to TSP_QUARTZ_LOCKS by:

INSERT INTO TSP_QRTZ_LOCKS values(NULL, 'STATE_ACCESS');

In case if the error will still occur, restart the server.

Please try this version and let us know if it The Scheduler is working properly after this.

Regards

[ChristianR]

After inserting all the 5 rows above I don't get an error any more in case I trigger an issue. Other TSP_* tables are also empty. Can you please check if they also need additional rows?

select * from TSP_QRTZ_BLOB_TRIGGERS; select * from TSP_QRTZ_CALENDARS; select * from TSP_QRTZ_CRON_TRIGGERS; select * from TSP_QRTZ_FIRED_TRIGGERS; select * from TSP_QRTZ_JOB_DETAILS; select * from TSP_QRTZ_JOB_LISTENERS; select * from TSP_QRTZ_PAUSED_TRIGGER_GRPS; select * from TSP_QRTZ_SIMPLE_TRIGGERS; select * from TSP_QRTZ_TRIGGERS; select * from TSP_QRTZ_TRIGGER_LISTENERS;

Are the rows normally added by the scheduler add-on or should this be done by the quarz installation?

[jost]

Most of this table should be empty if there are no Scheduled Jobs in JIRA. Do you mean that plugin working properly now? -please check whether issues are automatically fired.

Yes, The Scheduler should create these tables and fill it them during installation. It's was something wrong, however i cannot write what is the problem without seeing the whole logs. So if you have some more problems, please send us piece of logs contains whole installation till the error occurs.

[jost]

Hi Christian,

Could you confirm that the Scheduler is working properly now?

Regards.

[ChristianR]

Hi,

it works now.

Regards,

Christian

Gesendet: Montag, 17. August 2015 14:57 An: Christian Rossberg Betreff: Re: [Bitbucket] Issue #62: Scheduler does not trigger any more (apdc/the-scheduler)

ostrowskij https://bitbucket-assetroot.s3.amazonaws.com/c/photos/2015/Mar/12/2208279302-0-ostrowskij-avatar_avatar.png

ostrowskij commented on issue #62:

https://bitbucket.org/apdc/the-scheduler/issues/62/scheduler-does-not-trigger-any-moreScheduler does not trigger any moreHi Christian,Could you confirm that the Scheduler is working properly now?Regards. https://bitbucket.org/apdc/the-scheduler/issues/62/scheduler-does-not-trigger-any-more View this issue or add a comment by replying to this email. https://bitbucket.org/api/1.0/apdc/the-scheduler/issue/62/unwatch/crossberg/8f354b2a2d8de25a4c55e05dd01a881744f207ef/ Unwatch this issue to stopreceiving email updates. https://bitbucket.org/account/notifications/mark-read/189417193/8d6e17e24673af5a005a232d952e23dbb8a14dd2/ https://bitbucket.org Bitbucket