Eviction Policy and configuration issues

[spievak]

Hi, i´m having some problems with cache eviction. I have used the TreeCache implementation with the following configuration:

<?xml version="1.0" encoding="UTF-8"?>

<server>

 <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar"/>

 <mbean code="org.jboss.cache.TreeCache" name="jboss.cache:service=TreeCache">

 <depends>jboss:service=Naming</depends>
 <depends>jboss:service=TransactionManager</depends>

 <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
 <attribute name="CacheMode">LOCAL</attribute>

 <!-- Name of the eviction policy class. -->
 <attribute name="EvictionPolicyClass">org.jboss.cache.eviction.LRUPolicy</attribute>
 <!-- Specific eviction policy configurations. This is LRU -->
 <attribute name="EvictionPolicyConfig">
 <config>
 <attribute name="wakeUpIntervalSeconds">5</attribute>
 <!-- Cache wide default -->
 <region name="/_default_">
 <attribute name="maxNodes">1000</attribute>
 <attribute name="timeToLiveSeconds">10</attribute>
 </region>
 <region name="/teste">
 <attribute name="maxNodes">1000</attribute>
 <attribute name="timeToLiveSeconds">10</attribute>
 </region>
 </config>
 </attribute>
 </mbean>
</server>

I was expecting that with this config nodes with live greater than 10 seconds be collected by LRU policy and the be throwed away since there is not CacheLoader assigned.
But the node remains in cache after the assigned time.

the code used for testing:

cache.put(new Fqn(new Object[] { "/test", 1 }), "item", "1");
Thread.currentThread().sleep(30000);
System.out.println(cache.get(new Fqn(new Object[] { "/test", 1}), "item"));

Since the node was not removed i try removing it in code, as:

cache.put(new Fqn(new Object[] { "/test", 1 }), "item", "1");
cache.remove(new Fqn(new Object[] { "/teste", 1 }));
Thread.currentThread().sleep(30000);
System.out.println(cache.get(new Fqn(new Object[] { "/test", 1}), "item"));

And again the node remains in cache.

Any suggestions ???

Thanks.

[ben.wang]

Eviction now only works with String based Fqn. So try to construct fqn directly, e.g., "/test/1" to see if that makes any difference.

[confuz]

I don't know it is a bug or is my misunderstand.

Once the number of nodes not exceeds the maxNodes value in region, the ecvit policy will not check the timeToLiveSeconds and maxAgeSeconds values.

As my understand, timeToLiveSeconds and maxAgeSeconds should work regardless the number of nodes in region.

Ben, can clear this issue, thanks.

[ben.wang]

No, they are independent constraint. Eviction comes which ever condition is satisfied first (e.g., either maxNodes exceeds or timeToLiveSeconds is up).