-
Type: Bug
-
Status: Done
-
Priority: Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 1.17.0
-
Component/s: appng-core
-
Labels:None
In some environments, Ehcache seems not to properly shutdown it's replication threads.
WARNUNG: The web application [ROOT] appears to have started a thread named [Replication Thread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.lang.Thread.sleep(Native Method) net.sf.ehcache.distribution.RMIAsynchronousCacheReplicator.replicationThreadMain(RMIAsynchronousCacheReplicator.java:117) net.sf.ehcache.distribution.RMIAsynchronousCacheReplicator.access$000(RMIAsynchronousCacheReplicator.java:58) net.sf.ehcache.distribution.RMIAsynchronousCacheReplicator$ReplicationThread.run(RMIAsynchronousCacheReplicator.java:389)
Some experimenting has shown that it's sufficient to give those threads some time to detect their termination status.
- relates to
-
APPNG-2129 Thread [HSQLDB Timer] not stopped on application shutdown
- Done