upgraded to tomcat9 issues

Steve Herrera sherrera at fsmail.bradley.edu
Tue Sep 1 19:18:53 UTC 2020


Hello all,
I'm working on getting our IDP from version 3.4.7 ready to move forward to
4.0.1. I've fixed all the deprecated warnings. The OS was ubuntu 16.04LTS
and openjdk 8 with Tomcat 8. I ran the in-place upgrade to get me to 18.04
and that upgraded to openjdk11. Tomcat remained the same. The idp.war file
deployed and ran as expected. According to the Supported versions for idp4,
I must run Tomcat 9. I upgraded to Tomcat 9 and the idp stopped working.
There is nothing in the idp-process.log file. The tomcat logs show:

01-Sep-2020 13:57:45.840 SEVERE [main]
org.apache.catalina.core.StandardContext.startInternal One or more
listeners failed to start.

01-Sep-2020 13:57:45.842 SEVERE [main]
org.apache.catalina.core.StandardContext.startInternal Context [/idp]
startup failed due to previous errors

01-Sep-2020 13:57:45.883 WARNING [main]
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:

 java.base at 11.0.8/jdk.internal.misc.Unsafe.park(Native Method)

 java.base at 11.0.8
/java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)

 java.base at 11.0.8
/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2081)

 java.base at 11.0.8
/java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:417)


ch.qos.logback.core.AsyncAppenderBase$Worker.run(AsyncAppenderBase.java:289)

01-Sep-2020 13:57:45.884 WARNING [main]
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The
web application [idp] appears to have started a thread named [Timer-0] but
has failed to stop it. This is very likely to create a memory leak. Stack
trace of thread:

 java.base at 11.0.8/java.lang.Object.wait(Native Method)

 java.base at 11.0.8/java.util.TimerThread.mainLoop(Timer.java:553)

 java.base at 11.0.8/java.util.TimerThread.run(Timer.java:506)

01-Sep-2020 13:57:45.885 WARNING [main]
org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The
web application [idp] appears to have started a thread named [Timer for
org.opensaml.saml.metadata.resolver.impl.FileBackedHTTPMetadataResolver at 3e92cda3]
but has failed to stop it. This is very likely to create a memory leak.
Stack trace of thread:

 java.base at 11.0.8/java.lang.Object.wait(Native Method)

 java.base at 11.0.8/java.lang.Object.wait(Object.java:328)

 java.base at 11.0.8/java.util.TimerThread.mainLoop(Timer.java:527)

 java.base at 11.0.8/java.util.TimerThread.run(Timer.java:506)


I'm creating this upgrade path in our development environment so production
is not down. I've tested other war files and they deploy correctly. The
logs say one or more listeners failed to start, but tomcat is running on
the proper ports. Tomcat9 runs as a different user than Tomcat8 did but the
permissions were changed for that. I've tried removing Tomcat8 prior to
installing Tomcat9 and get the same results.


Has anyone run into something like this?


Steve Herrera
System Administration
Information Security
Bradley University
Phone: 309 / 677-2336
FAX: 309 / 677-3460
Email:  *sherrera at fsmail.bradley.edu <sherrera at fsmail.bradley.edu>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20200901/b24759f3/attachment.htm>


More information about the users mailing list