It is async for disk cache right now, in AbstractDiskCache:
/**
* @see org.apache.jcs.engine.behavior.ICache#remove
*/
public final boolean remove( Serializable key )
{
// Remove element from purgatory if it is there
purgatory.remove( key );
// Queue removal for persistent store
try
{
cacheEventQueue.addRemoveEvent( key );
}
catch ( IOException e )
{
log.error( e );
cacheEventQueue.destroy();
}
return false;
}
That is my doing, easily fixed, one sec =]
On Tue, 2002-05-14 at 13:34, Aaron Smuts wrote:
> Hmmn. It didn't work with destroy either.
>
> I'm looking into the remove call. Removal should be synchronous for disk.
> For other auxiliaries it is async.
>
> > -----Original Message-----
> > From: James Taylor [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, May 14, 2002 1:14 PM
> > To: Turbine JCS Developers List
> > Subject: Re: cvs commit: jakarta-turbine-jcs/src/test/org/apache/jcs
> > TestDiskCacheConcurrent.java
> >
> >
> > > I can't tell why the test disk concurrent test fails.
> >
> > Interesting. Once you changed destroy to remove (which makes perfect
> > sense) it no longer works. I did the same for TestDiskCache with the
> > same result. This appears to be because removals are async, and the item
> > is still available on the DiskCache. Should removals from the disk cache
> > be async? No real way to predict when the removal will be done =/
> >
> >
> > --
> > To unsubscribe, e-mail: <mailto:turbine-jcs-dev-
> > [EMAIL PROTECTED]>
> > For additional commands, e-mail: <mailto:turbine-jcs-dev-
> > [EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
