2014-11-27 17:41:07,460 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] Checking the interval for service: GT Deadline reached at Thu Nov 27 17:41:07 CET 2014 2014-11-27 17:41:07,460 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] run service GT Deadline reached: 1 elapsed 2014-11-27 17:41:07,461 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] Execute service: GT Deadline reached 2014-11-27 17:41:07,463 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] Issues returned by query (status = Waiting AND ( Deadline <= endOfDay() OR updatedDate <= endOfDay(-14) )): [] 2014-11-27 17:42:07,457 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] Checking the interval for service: GT Deadline reached at Thu Nov 27 17:42:07 CET 2014 2014-11-27 17:42:07,458 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] Not firing service GT Deadline reached: 0 elapsed < 1 interval. 2014-11-27 17:43:07,459 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] Checking the interval for service: GT Deadline reached at ThuNov 27 17:43:07 CET 2014 2014-11-27 17:43:07,459 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] run service GT Deadline reached: 1 elapsed 2014-11-27 17:43:07,459 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] Execute service: GT Deadline reached 2014-11-27 17:43:07,462 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] Issues returned by query (status = Waiting AND ( Deadline <= endOfDay() OR updatedDate <= endOfDay(-14) )): [] 2014-11-27 17:44:07,459 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] Checking the interval for service: GT Deadline reached at Thu Nov 27 17:44:07 CET 2014 2014-11-27 17:44:07,460 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] run service GT Deadline reached: 1 elapsed 2014-11-27 17:44:07,460 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] Execute service: GT Deadline reached 2014-11-27 17:44:07,463 atlassian-scheduler-quartz1.local_Worker-1 DEBUG service-bot [canned.jira.admin.EscalationService] Issues returned by query (status = Waiting AND ( Deadline <= endOfDay() OR updatedDate <= endOfDay(-14) )): [] 2014-11-27 17:45:07,459 atlassian-scheduler-quartz1.local_Worker-1 DEBUG ServiceRunner [canned.jira.admin.EscalationService] Checking the interval for service: GT Deadline reached at Thu Nov 27 17:45:07 CET 2014 2014-11-27 17:45:07,460 atlassian-scheduler-quartz1.local_Worker-1 DEBUG ServiceRunner [canned.jira.admin.EscalationService] run service GT Deadline reached: 1 elapsed 2014-11-27 17:45:07,460 atlassian-scheduler-quartz1.local_Worker-1 DEBUG ServiceRunner [canned.jira.admin.EscalationService] Execute service: GT Deadline reached 2014-11-27 17:45:07,469 atlassian-scheduler-quartz1.local_Worker-1 DEBUG ServiceRunner [canned.jira.admin.EscalationService] Issues returned by query (status = Waiting AND ( Deadline <= endOfDay() OR updatedDate <= endOfDay(-14) )): [GT-12, AOD-8]
Hi,
I figure out the same problem. As teh Script Runner does not run the Escalation Service, I searched for any entries in the services table. (i also remeber, that there was at least one entry for the escalation service).
But now, there is neither an entry, nor the services are called. (i set one of them to 1 min repeating, but nothing happend->tail -f éd the log). Any of the services are callable manually, so the script itself is running.
From all this I conclude, that there might be an error, creating the service definitions in JIRA by the runner?
Hi Andreas, I hope you are not running into this issue - https://jamieechlin.atlassian.net/browse/GRV-383 ,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, I dont think so, there are not some servcie calls missing, but ALL of them.. there is no service defined in Jira Service registry
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas,
Did you get it fixed??
You have mentioned - "
But the escalation service is located in the "Built-in" script section of the script runner plugin -
myjira.com/admin/groovy/CannedScriptRunner!default.jspa and then click on escalation services
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Take a look at serviceconfig table and see if there is an entry in there which is not showing up in the Services admin UI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is no entry for the script runner or an escalation service in the table: {code} mysql> select * from serviceconfig; +-------+-----------+----------------------------------------------------------------------+----------------------------+ | ID | delaytime | CLAZZ | servicename | +-------+-----------+----------------------------------------------------------------------+----------------------------+ | 10000 | 60000 | com.atlassian.jira.service.services.mail.MailQueueService | Mail Queue Service | | 15215 | 60000 | com.atlassian.jira.service.services.mail.MailFetcherService | Standard Mail Handler | | 15300 | 86400000 | com.atlassian.jira.service.services.auditing.AuditLogCleaningService | Audit log cleaning service | +-------+-----------+----------------------------------------------------------------------+----------------------------+ 3 rows in set (0.00 sec) {code}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.