This content has been marked as final.
Show 4 replies
-
1. Re: Timeout on node -- possible??
manik Mar 5, 2009 5:25 AM (in response to krishnan366)Configure an expiration policy. This way you can specify when objects expire. In addition, you should change the EvictionActionPolicy from the default (only evict from memory) to the RemoveOnEvictActionPolicy.
-
2. Re: Timeout on node -- possible??
krishnan366 Mar 6, 2009 1:24 AM (in response to krishnan366)Hi Manik,
Thanks for the response. I am using cache-config.xml to set the cache configuration options. How do I change to RemoveOnEvictActionPolicy in the config file .
Also the node should also be saved to database if the cache memory exceeds or may be when the number of nodes exceed a certain limit. This is right now configured and is working fine.
Can this be coupled with the RemoveOnEvictActionPolicy to achieve both ? -
3. Re: Timeout on node -- possible??
krishnan366 Mar 12, 2009 5:14 AM (in response to krishnan366)Thanks Manik, I was able to find out on configuring RemoveOnEvictActionPolicy. it is as follows
<region name="/org/jboss/data2" actionPolicyClass="org.jboss.cache.eviction.RemoveOnEvictActionPolicy"> 27 <attribute name="maxNodes">5</attribute> <property name="maxNodes" value="5"/> 28 <attribute name="timeToLive">4000</attribute> <property name="timeToLive" value="4000"/> 29 </region> </region>
-
4. Re: Timeout on node -- possible??
krishnan366 Mar 12, 2009 5:15 AM (in response to krishnan366)<region name="/org/jboss/data2" actionPolicyClass="org.jboss.cache.eviction.RemoveOnEvictActionPolicy"> <property name="maxNodes" value="5"/> <property name="timeToLive" value="4000"/> </region>