jakarta-jcs-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Cronin" <tcro...@interwoven.com>
Subject RE: cache corruption
Date Wed, 13 Feb 2008 20:55:19 GMT
We are using indexed disk cache and the keys are all Strings.

we only call JCS.put, JCS.get, JCS.remove we never muck with the
CacheElement.

the way we saw the mix up was when we viewed the cache from
the JCSAdmin page and typing the keys in to the query field
the key wasn't showing up in the mem cache keys listing on
the details page.

this is happening at a customer site and I haven't been able to
reproduce the problem locally, but cache code is all
blacked boxed as far as the customer is concerned.

I've attached the ccf in case we've configured it improperly
(ive been digging through the docs to make sure I've set
thing correctly)

As soon as I can get more information I will post.


-----Original Message-----
From: Aaron Smuts [mailto:asmuts@yahoo.com] 
Sent: Wednesday, February 13, 2008 2:09 PM
To: JCS Users List
Subject: Re: cache corruption

I've never seen anything like this happen.  I need
more details.  What auxiliaries are you using?  Are
all the keys strings?  

Please double check the code that is putting the items
in the cache.  Perhaps the problem is there.

Aaron


--- Tim Cronin <tcronin@interwoven.com> wrote:

> We use jcs (1.3) in a web application, and over time
> we're seeing where
> 
> two different keys (string based key) point to the
> same object
> 
> say we have key "a" key "b" if I call
> JCS.getCacheElement("a")
> 
> I get the element where the key = "b". I then call
> 
> JCS.remove("b") then call JCS.get("b") I get null
> 
> but if I call JCS.get("a") I get the object cached
> for "b"
> 
> and subsequent calls to JCS.get("b") now return the
> object.
> 
> only if call JCS.remove("a") will the problem be
> fixed.
> 
> it also seems to "right" itself over time I believe
> if it
> get dropped from the cache.
> 
> I was able to see the key mismatch using the
> JCSAdmin.jsp
> to interrogate the cache.
> 
> I'm trying to track down exactly when this happens.
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
> 
> 


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




Mime
View raw message