Tomcat/JIRA Startup consistently hangs on schedule service recycle

[Clive Dickson]

We have a regular Tomcat service recycle as part of regular server maintenance (Windows 2008 R2) - done via a scheduled task. When the service is restarted, the Tomcat/JIRA startup goes as far as the step...

...

D: APPS Atlassian JIRA home plugins .bundled-plugins streams-jira-plugin-5.1.0.jar (1331853130000) created

2012-12-30 22:01:27,732 Thread-2 INFO atlassian.plugin.loaders.ScanningPluginLoader Plugin Unit: D: APPS Atlassian JIRA home plugins .bundled-plugins streams-spi-5.1.0.jar (1331853132000) created

2012-12-30 22:01:27,826 Thread-2 INFO atlassian.plugin.loaders.ScanningPluginLoader Plugin Unit: D: APPS Atlassian JIRA home plugins .bundled-plugins streams-thirdparty-plugin-5.1.0.jar (1331853132000) created

2012-12-30 22:01:27,873 Thread-2 INFO atlassian.plugin.loaders.ScanningPluginLoader Plugin Unit: D: APPS Atlassian JIRA home plugins .bundled-plugins workflow-designer-plugin-2.5.4.jar (1331853130000) created

... and just hangs. This is happening conistently more than 50% of the time leading to JIRA unavailability for our users. We can manually restart the service to clear the issue but this is manual intervention we would rather not do.

Please advise.

Tomcat/JIRA Startup consistently hangs on schedule service recycle

[Clive Dickson · Accepted solution]

Thanks - I could believe this if the point of hanging was different, but it is always at the point of loading the workflow designer jar... so I guess we are hitting some memory threshold each time at this point.

We are due to upgrade Tomcat and JIRA in the next month or so, so will look at these options if we still have a problem.

[David Chan]

In general, there are a few things that can cause this:

1. Starting JIRA can be fairly resource intensive on the disk, CPU and memory. If JIRA cannot get enough resources to load within the alloted plugin timer, then startup will fail
2. If your system has any anti-virus software (or other applications), it may be causing issues for JIRA upon startup, locking up needed resources/files

Another thing you can try is increasing the plugin timeouts during startup. The parameter would look something like this:

• -Datlassian.plugins.enable.wait=300