AW: The web application [idp] appears to have started a thread named [Thread-29] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

[ERLER Peter]

I had similar problems with IdP 3.3.1 on Apache Tomcat/8.5.14.

Specs:
JVM Version:           1.8.0_121-b31
OS Version:            3.10.0-514.10.2.el7.x86_64


07-Jun-2017 20:09:26.698 WARNING [http-nio-8080-exec-5] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [idp] appears to have started a thread named [Abandoned con
nection cleanup thread] 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.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
com.mysql.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:43)
07-Jun-2017 20:09:26.698 WARNING [http-nio-8080-exec-5] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [idp] appears to have started a thread named [AsyncAppender
-Worker-ASYNC_PROCESS] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:403)
ch.qos.logback.core.AsyncAppenderBase$Worker.run(AsyncAppenderBase.java:250)


The problems are gone since update to

JVM Version:           1.8.0_131-b31
OS Version:            3.10.0-514.21.1.el7.x86_64


Peter

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170705/efc58ada/attachment.html>