Skip to Content.
Sympa Menu

grouper-users - [grouper-users] Tomcat shut down its network protocol handlers, it's still hanging around due to the database threads

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] Tomcat shut down its network protocol handlers, it's still hanging around due to the database threads


Chronological Thread 
    < Chronological >      < Thread >
  • From: Siju Jacob <>
  • To: " Mailing List" <>
  • Subject: [grouper-users] Tomcat shut down its network protocol handlers, it's still hanging around due to the database threads
  • Date: Thu, 21 Mar 2019 19:38:28 +0000

Hi Team,

    We are using grouper 2.3 and came across another issue today.

 

   Shutting down the tomcat doesn’t shutdown all the db connections in connection pool. Are we missing something while shutting down the tomcat.

 

It looks like even though Tomcat shut down its network protocol handlers, it's still hanging around due to the database threads:

 

21-Mar-2019 14:35:17.050 WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [grouper] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->1br81mda110cbcl21eagx71|3fa3a73c]-HelperThread-#2] 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)
 com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:683)

 

Thanks,

Siju


Archive powered by MHonArc 2.6.19.

Top of Page