JIRA failed to shut down due to some plugin

My JIRA 6.1.5 runs on Tomcat 7.0.29, Oracle Linux 6.4. When stopping Tomcat, I get this message in catalina.out

2014-04-03 15:29:58,654 localhost-startStop-2 INFO      [atlassian.jira.startup.DefaultJiraLauncher] Stopping launchers
2014-04-03 15:29:58,655 localhost-startStop-2 INFO      [service.services.file.AbstractMessageHandlingService$HandlerDisablementListener] Unregistering disablement listener for module 'com.atlassian.jira.jira-mail-plugin:createIssueHandler'
2014-04-03 15:29:58,671 localhost-startStop-2 INFO      [atlassian.plugin.manager.DefaultPluginManager] Shutting down the plugin system
Interrupted background thread: JSPWiki Lucene Indexer.
Interrupted background thread: JSPWiki RSS Generator.
Interrupted background thread: WatchDog for 'Wiki'.
2014-04-03 15:29:59,466 Timer-2 INFO      [plugins.dvcs.listener.DvcsAddUserListener] Attempting to unregister listener ...
2014-04-03 15:29:59,467 Timer-2 INFO      [plugins.dvcs.listener.DvcsAddUserListener] Listener unregistered ...
2014-04-03 15:29:59,516 Timer-2 INFO      [plugins.dvcs.scheduler.DvcsScheduler] DvcsScheduler job unscheduled
2014-04-03 15:30:11,045 localhost-startStop-2 ERROR      [internal.util.concurrent.RunnableTimedExecution] Closing runnable for context NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.plugin.ext.subversion.atlassian-jira-subversion-plugin, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
2014-04-03 15:30:21,045 localhost-startStop-2 ERROR      [internal.util.concurrent.RunnableTimedExecution] Closing runnable for context NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.plugins.remote-link-aggregator-plugin, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs
2014-04-03 15:30:31,046 localhost-startStop-2 ERROR      [internal.util.concurrent.RunnableTimedExecution] Closing runnable for context NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.plugins.jira-remote-link-aggregator-plugin, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs

ERROR repeats and Tomcat is still alive. I don't want to use force method of stopping Tomcat. Instead of that I would like to know what is wrong with JIRA, that it prevents Tomcat to stop.

Leoš

Leoš Junek, system administrator, Prague, the Czech Republic

Updated at 3rd Apr 2014, 15:36 CEST (13:36 UTC): Message from catalina.out was presented in its all beauty, not only discussed ERROR, but also messages coming before this ERROR.

3 answers

1 accepted

Solved by Atlassian Support engineer at https://support.atlassian.com

  1. Finding out whether the problem is caused by Atlassian implicit plugin or by custom installed plugin. Steps: Administration > Manage Add-ons > click on link Enable Safe Mode. In safe mode all user (custom installed) plugins are disabled. Shutdown of Tomcat application server was very quick, so problem had to be caused by user installed plugin.
  2. Specifying of problematic user installed plugin. In Administratin > Manage Add-ons there is a filter that helps you to display only user installed plugins. Use it. Then disable all user installed plugins and enable the last one. Wait a while (a minute) after enabling just to let it be loaded. Then shutdown Tomcat server. Observe whether shutdown takes a long time or not. If it takes, this is your problematic plugin, if not, start Tomcat, log in to JIRA and enable the last but one plugin and shut down Tomcat again, while measuring shutdown time. Repeat enabling plugins one-by-one together with restarting Tomcat to find out problematic plugin. Then ask experts to help you with problematic plugin. Let plugin shut down.

Thanks, but it did not help. Tomcat does not stop though when (Tomcat was) stopped by kill -15 PID, two mentioned directories were removed and Tomcat started.

Hi Leos,

We are on Jira 6.2.7 and have similar issue. All this started after we installed the Agile plugin(my guess not 100% sure if this causes the issue). Do you have the Agile plugin? Is your issue solved?

Thanks

Priya

Any updates on the above? We have similar issue.

No, I do not worry about it. Tomcat is shutted down with -force option. In fact, it is not solved. We do not have any Agile plugin. In our case it was probably SVN plugin, but I do not care now.

Any updates on this? We are facing same issue after upgrading to JIRA6.4.8

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,958 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot