Script Runner escalation service does not find issues (switches users)

Thomas Heidenreich
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 27, 2014
I´ve got a really stage behaviour of the escalation service:
  • configured to use the user "service-bot" which can find 2 issues when logging in with it
  • the escalation service takes most of the time this user and finds no issues - sometimes (about every 3rd run) it uses a "ServiceRunner" as actor and finds the issues
  • In JIRA -> System -> Services there is no entry from script runner (I remember seeing them there before 3.0)
Versions are
  • JIRA 6.3.10
  • Script Runner 3.0.6

 

Debug Log from Script Runner:
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]

 

 

3 answers

0 votes
Andreas Haaken December 31, 2014

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?

Tarun Sapra
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 14, 2015

Hi Andreas, I hope you are not running into this issue - https://jamieechlin.atlassian.net/browse/GRV-383 ,

Andreas Haaken January 14, 2015

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

0 votes
Tarun Sapra
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 9, 2014

Hi Thomas,

 

Did you get it fixed??

You have mentioned - "

  • In JIRA -> System -> Services there is no entry from script runner (I remember seeing them there before 3.0)"

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

0 votes
Boris Berenberg
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 28, 2014

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.

Thomas Heidenreich
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 8, 2014

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}

Suggest an answer

Log in or Sign up to answer