jakarta-jcs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Estefano Eduardo" <eduardo.estef...@siemens.com>
Subject RE: Tomcat + JCS shutdown problem
Date Mon, 12 Jul 2004 09:35:57 GMT
Indeed the dispose kills the schrinker. But who is calling the
dispose(). The MemoryCache interface has no dispose() method declare. I
see the CompositeCache holds a reference to the MemoryCache (not
AbstractMemoryCache). The CompositeCache iterates the auxiliary caches
calling dispose() on each one. But I don't see the CompositeCache
casting MemoryCache to AbstractMemoryCache and then calling dispose on
it.

I'm relatively new to the source code so maybe I'm missing something. As
far as I can see there should be a dispose() method declared on
MemoryCache interface and CompositeCache needs to call dispose on the
memoryCache reference within its dispose() method.

-----Original Message-----
From: Aaron Smuts [mailto:aasmuts@wisc.edu] 
Sent: Saturday, 10 July, 2004 5:17
To: 'Turbine JCS Developers List'
Subject: RE: Tomcat + JCS shutdown problem


http://jakarta.apache.org/turbine/jcs/xref/org/apache/jcs/engine/memory/
AbstractMemoryCache.html


The dispose should kill the shrinker.

Cheers,

Aaron

> -----Original Message-----
> From: Estefano Eduardo [mailto:eduardo.estefano@siemens.com]
> Sent: Friday, July 09, 2004 4:38 AM
> To: Turbine JCS Developers List
> Subject: RE: Tomcat + JCS shutdown problem
> 
> Are you sure about this? I still don't see a dispose() method in the 
> MemoryCache Interface after I get latest version from CVS. Maybe this
is
> implemented in another branch?
> 
> I also don't see any calls to AbstractMemoryCache.dispose() right now.
> 
> One more thing, there is a IMemoryCache and a MemoryCache Interfaces.
It
> looks like the MemoryCache is used at the moment. This should be
removed
> and replaced with the IMemoryCache for consistency. They look pretty 
> much the same right now.
> 
> -----Original Message-----
> From: Aaron Smuts [mailto:aasmuts@wisc.edu]
> Sent: Friday, 09 July, 2004 1:14
> To: 'Turbine JCS Developers List'
> Subject: RE: Tomcat + JCS shutdown problem
> 
> 
> This fix should be in cvs.
> 
> Aaron
> 
> > -----Original Message-----
> > From: Estefano Eduardo [mailto:eduardo.estefano@siemens.com]
> > 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:aasmuts@wisc.edu]
> > 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:Corin.Moss@tvnz.co.nz]
> > > Sent: Thursday, July 08, 2004 12:46 AM
> > > To: jakarta-turbine-jcs-dev@apache.org
> > > 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:
> turbine-jcs-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail:
> > turbine-jcs-dev-help@jakarta.apache.org
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
turbine-jcs-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> turbine-jcs-dev-help@jakarta.apache.org
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
turbine-jcs-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> turbine-jcs-dev-help@jakarta.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-jcs-dev-help@jakarta.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
turbine-jcs-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-dev-help@jakarta.apache.org


Mime
View raw message