Jamie,
I wrote the code you're having issues with.
This is definitely a bug.
http://jira.jboss.com/jira/browse/JBCACHE-1051
If you have an elegant solution (patch) it would be appreciated. This will
definitely get fixed in the next release, however, elegant or not.
View the original post :
The most elegant solution I could come up with is to never delete the
ExpirationEntry, but double-check the node's current expiration value before
eviction. The solution looks like this:
| Index: src/org/jboss/cache/eviction/ExpirationAlgorithm.java
|
I don't have a more elegant solution. Thanks for the fix!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4044356#4044356
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4044356
___
