This fix should be in cvs.  

Aaron

> -----Original Message-----
> From: Estefano Eduardo [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 08, 2004 6:59 AM
> To: Turbine JCS Developers List
> Subject: RE: Tomcat + JCS shutdown problem
> 
> I think there is still the problem with the Schrink Threads also, not
> sure if it is related. The AbstractMemoryCache now has a call to stop
> the schrinker, but there is no interface for the dispose() method in
the
> MemoryCache interface. At shutdown, the CompisteCache only calls
> dispose() on auxiliary caches and not on the memory cache.
> 
> I added the dispose() to the MemoryCache and updated CompositeCache to
> also call memCache.dispose() and now finally the Schrinkers are gone
> when I stop my application.
> 
> Eduardo
> 
> -----Original Message-----
> From: Aaron Smuts [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 08 July, 2004 13:57
> To: 'Turbine JCS Developers List'
> Subject: RE: Tomcat + JCS shutdown problem
> 
> 
> Are you disposing of all regions at shutdown?  You can get the list of
> regions from the cache manager and dispose each in the destroy method
of
> a startup servlet.
> 
> I'll try to confirm that the dispose is working properly.
> 
> Aaron
> 
> > -----Original Message-----
> > From: Corin Moss [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, July 08, 2004 12:46 AM
> > To: [EMAIL PROTECTED]
> > Subject: Tomcat + JCS shutdown problem
> >
> >
> > Hi Guys,
> >
> > We've spent the last couple of days debugging a Tomcat shutdown
> problem.
> > We've traced the problem to our use of the JCS Remote Cache.  When
we
> > configure the remote cache to talk to another server, the listener
> port
> > that is opened within Tomcat (to enable loopback communication)
> prevents
> > Tomcat from shutting down (as the port is still bound as a Server
> > Listener to the remote cache.)
> >
> >
> > Can anyone think of a way to ensure that Tomcat can instruct JCS to
> > close down the Server Listener cleanly?
> >
> > Thanks,
> >
> > Corin
> >
> > ================================================================
> > CAUTION: This e-mail and any attachment(s) contains information that
> > is intended to be read only by the named recipient(s). It may
contain
> > information that is confidential, proprietary or the subject of
legal
> > privilege. This information is not to be used by any other person
> > and/or organisation. If you are not the intended recipient, please
> > advise us immediately and delete this e-mail from your system. Do
not
> > use any information contained in it.
> >
> > ================================================================
> > For more information on the Television New Zealand Group, visit us
> > online at http://www.tvnz.co.nz
> > ================================================================
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
[EMAIL PROTECTED]
> > For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
[EMAIL PROTECTED]
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
[EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to