here's the my-config again...
attribute name="EvictionPolicyClass" org.jboss.cache.eviction.LRUPolicy attribute
attribute name="wakeUpIntervalSeconds" 5 /attribute
attribute name="maxNodes" 5000 /attribute
attribute name="timeToLiveSeconds" 3 /attribute
attribute name="maxAgeSeconds" 5 /attribute
attribute name="maxNodes" 1000 /attribute
attribute name="timeToLiveSeconds" 2 /attribute
attribute name="maxAgeSeconds" 3 /attribute
argh... i cannot edit my post...
String s = (String)tree.get("/fandango/1","5sec");
String s = (String)tree.get("/test/1","5sec");
maxAgeSeconds has been deprecated long time ago (since 1.2) for timeToLiveSeconds.
Try to run the junit test under the distro. Under evict, it has numerous examples illustrating the eviction policy expiration test.
I found my problem was with "wakeUpIntervalSeconds" value being set too long.
I am trying to use JBoss Tree Cache AOP for caching startup data, so my question is is it by default configured for Clustered environment, if not what I have to do for clustered environment. Moreover if I am able to use TreeCacheAOP without starting JBoss server, it's not giving me feeling that cache resides in server I know I am totally wrong but I amn't able to get clear picture of JBoss Tree Cache AOP, can you guys point me to a place where I can get clear picture.