Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of tim@outboundengine.com
 designates 209.85.214.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOGo0VbWwmnMWJDD_L9ZOCZhODAE3zX4NGRJfCmRF+NRs2hj3w@mail.gmail.com>
References: 
 <CAGqxDxJxKGwQF8oiB6NzraMgjyi4pRtQg+Lx7rMjJhGMjNwfXQ@mail.gmail.com>
	<CAOGo0VbWwmnMWJDD_L9ZOCZhODAE3zX4NGRJfCmRF+NRs2hj3w@mail.gmail.com>
Date: Thu, 22 Jan 2015 12:39:25 -0600
Message-ID: 
 <CAGqxDx+d30ftyrOpSbsb4+Hu9gcEQjJ7-MKttXmUf+W63dNdLQ@mail.gmail.com>
Subject: Re: JSC 1.3 thread cleanup
From: Tim Cronin <tim@outboundengine.com>
To: Commons Users List <user@commons.apache.org>
Content-Type: multipart/alternative; boundary=001a113d0944d305aa050d41fd11

--001a113d0944d305aa050d41fd11
Content-Type: text/plain; charset=UTF-8

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 <sebbaz@gmail.com> wrote:

> On 22 January 2015 at 16:42, Tim Cronin <tim@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-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>

--001a113d0944d305aa050d41fd11--