-
Type:
Bug
-
Resolution: Low Engagement
-
Priority:
Low
-
None
-
Affects Version/s: 6.2.7
-
Component/s: Installation
-
6.02
-
1
-
Severity 3 - Minor
-
0
Re:Inception
When doing upgrades/uninstalls we need to stop jira and then perform some operations, backup dirs on upgrade and delete files and user account on uninstall.
We have noticed that quite often jira will not stop in timely fashion and on some occasion it will run forever.
INFO: Stopping service Catalina Apr 18, 2011 6:01:49 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [QuartzWorker-0] but has failed to stop it. This is very likely to create a memory leak. Apr 18, 2011 6:01:49 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [QuartzWorker-1] but has failed to stop it. This is very likely to create a memory leak. Apr 18, 2011 6:01:49 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Spring executor 1] but has failed to stop it. This is very likely to create a memory leak. Apr 18, 2011 6:01:49 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Spring executor 2] but has failed to stop it. This is very likely to create a memory leak. Apr 18, 2011 6:01:49 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap SEVERE: The web application [] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@67ad79]) and a value of type [org.dom4j.DocumentFactory] (value [org.dom4j.DocumentFactory@ae00e3]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.
Attached is the log file with the problems reported on shutdown and the threaddumps taken after stop script was called but jira was still running (there are several start/stops included in the file).
I noticed that jira was running forever after we did uninstall, i.e. after the shutdown was called and then all files (apart from log files) deleted.