-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 4.1.1, 5.1.6, 5.2.6, 5.2.11, 6.1, 6.1.2
-
Component/s: UPM (Universal Plugin Manager)
-
4.01
Occasionally JIRA takes longer than usual to shut down. The log contains
Aug 19, 2010 9:07:28 AM org.apache.coyote.http11.Http11BaseProtocol pause INFO: Pausing Coyote HTTP/1.1 on http-8080 Aug 19, 2010 9:07:29 AM org.apache.catalina.core.StandardService stop INFO: Stopping service Catalina 2010-08-19 09:07:30,650 ConnectionKeeper-1 INFO [atlassian.jira.upgrade.ConnectionKeeper] Shutting down. 2010-08-19 09:07:31,040 main INFO [atlassian.plugin.manager.DefaultPluginManager] Shutting down the plugin system 2010-08-19 09:07:55,466 main ERROR [internal.util.concurrent.RunnableTimedExecution] Closing runnable for context OsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.gadgets, 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 2010-08-19 09:07:58,023 main INFO [atlassian.jira.startup.JiraStartupChecklistContextListener] Unlocking JIRA Home log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository. Aug 19, 2010 9:07:58 AM org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8080
1. Why does this happen?
2. What can I do to prevent it?
3. Please can the answers to 1 and 2 be added to the documentation somewhere.
- relates to
-
-
- Gathering Impact
-
- is caused by
-
UPM-4058 Loading...