it's not a tomcat error, it's a JCS resource leak tomcat is showing the error but it's caused by JCS not cleaning up the threads it's creating.
On Thu, Jan 22, 2015 at 11:46 AM, sebb <seb...@gmail.com> wrote: > On 22 January 2015 at 16:42, Tim Cronin <t...@outboundengine.com> wrote: > > I'm getting tomcat errors on shutdown: > > This is the Commons User mailing list. > > Please subscribe to the Tomcat User mailing list and ask there. > > > 2015-01-22 16:41:51,186 [localhost-startStop-2] ERROR > > org.apache.catalina.loader.WebappClassLoader- The web application > > [/api] appears to have started a thread named > > [ElementEventQueue.QProcessor-1] but has failed to stop it. This is very > l > > ikely to create a memory leak. > > > > i tracked it down to > > > > org.apache.jcs.engine.control.CompositeCache: > > > > /** > > * EventQueue for handling element events. 1 should be enough for all > > the regions. Else should > > * create as needed per region. > > */ > > public static IElementEventQueue elementEventQ = new > ElementEventQueue( > > "AllRegionQueue" ); > > > > then calling CompositeCache.elementEventQ.destroy(); > > > > but it can be flaky and IMO should be handled via > > CompositeCacheManager.shutdown(). > > > > is there a better way to handle this and do i need to file a bug on this? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org > For additional commands, e-mail: user-h...@commons.apache.org > >
