Chris sing a song for us. Em 04/03/2016 16:13, "Chris Brown" <chris_br...@ncci.com> escreveu:
> Tomcat version: 7.0.42 > Server OS: Sun Solaris > UCP Version: Oracle 12c > Oracle Driver: ojdbc7 > JDK version: 1.8.0_31 > > Issue Description: > When tomcat shuts down our web service during a hot deployment threads are > left running that tomcat cannot shutdown. I believe the threads are from > the universal connection pool. We use oracle's universal connection pool > (ucp.jar). After multiple deployments the threads build up and cause high > CPU usage from the 2 tomcat threads. > > Log Error Examples: > Feb 08, 2016 8:00:25 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [/RatingService] appears to have started a > thread named [UCP-worker-thread-3] but has failed to stop it. This is very > likely to create a memory leak. > Feb 08, 2016 8:00:25 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [/RatingService] appears to have started a > thread named [Thread-438] but has failed to stop it. This is very likely to > create a memory leak. > Feb 27, 2016 6:15:14 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [/RatingService] appears to have started a > thread named > [oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockReleaser] > but has failed to stop it. This is very likely to create a memory leak. > Feb 27, 2016 6:15:14 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [/RatingService] appears to have started a > thread named [ForkJoinPool.commonPool-worker-32] but has failed to stop it. > This is very likely to create a memory leak. > Feb 27, 2016 6:15:14 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > SEVERE: The web application [/RatingService] appears to have started a > thread named [Timer-121] but has failed to stop it. This is very likely to > create a memory leak. > > Correction made to code to try and fix issue: > I added a ServletContextListener to our web service. On the > contextDestroyed method we destroy the connection pools. Our web service > uses 2 connection pools. > > I also upgraded to Tomcat 8 and the issue still occurred, but the messages > are now warnings instead of SEVERE errors. > > I've searched the web and have tried many suggestions that have not helped > except destroying the connection pools, but the issue still occurs. Please > help!!! > > Thank you, > Chris Brown > Systems Consultant > National Council on > Compensation Insurance > 901 Peninsula Corporate Circle > Boca Raton, FL 33487-1362 > (P) 561-893-2324 > chris_br...@ncci.com > > > > ________________________________ > > The information contained in this e-mail message is intended only for the > personal and confidential use of the recipient(s) named above. This message > may be an attorney-client communication and/or work product and as such is > privileged and confidential. If the reader of this message is not the > intended recipient or an agent responsible for delivering it to the > intended recipient, you are hereby notified that you have received this > document in error and that any review, dissemination, distribution, or > copying of this message is strictly prohibited. If you have received this > communication in error, please notify us immediately by e-mail, and delete > the original message. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
