PSMQ causes delay during JIRA startup

Experienced Behavior

During JIRA Service Desk automation startup PSMQ checks for outstanding jobs that need to reexecute. This task is performed by the localhost-startStop-1 thread and delays startup of the entire JIRA instance.

• The delay may range from less than a second to multiple minutes depending on the number of entries that PSMQ checks.

Log entries associated with this are included below. This example shows a delay of over nine minutes.

2017-06-25 09:41:35,892 localhost-startStop-1 INFO      [c.a.s.p.a.internal.bootstrap.AutomationPluginLauncher] AutomationPlugin onStart() - Service Desk Automation Plugin is starting...
2017-06-25 09:41:35,914 localhost-startStop-1 DEBUG      [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.psmq]
2017-06-25 09:51:03,885 localhost-startStop-1 INFO      [c.a.s.p.a.internal.bootstrap.AutomationPluginLauncher] AutomationPlugin onStart() - Service Desk Automation Plugin is started.

Expected Behavior

JIRA Service Desk Automation and PSMQ do not cause multiple minute delay when starting JIRA.

Steps to Reproduce

• Create instance with JIRA Service Desk 3.5.0 or newer.
• Create requests
• Trigger an automation rule for each request
• Restart JIRA
• Monitor startup logging for "AutomationPlugin onStart()" and observe delay between "starting" and "started" entries

Length of delay will depend on number of issues.

• ~600 issues shows 2sec delay
• ~1200 requests show 4sec delay
• Longest delay observed is over 10 minutes. Instance containing 100,000+ requests.