[MAGNOLIA-6951] ClockDaemon very likely memory leak Created: 06/Feb/17 Updated: 06/Feb/17 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 5.5.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Ronald Ten Berge | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Tomcat 8.5.11, OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-2~bpo8+1-b14) |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
A shutdown/redeploy of our production Magnolia 5.5.1 instance results in a large number of the following warning messages from Tomcat. This happens on the public and author instances. WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [magnoliaAuthor] appears to have started a thread named [Thread-46] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:502) EDU.oswego.cs.dl.util.concurrent.ClockDaemon.nextTask(Unknown Source) EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(Unknown Source) java.lang.Thread.run(Thread.java:745) It seems that the EDU.oswego.cs.dl.util.concurrent.ClockDaemon#shutDown() is never being called from DelayedExecutor to clean-up these threads. |