Hello,
I'm trying to run the clusterstore EJB3 TrailBlazer POJO Clustering and Caching demo application.
The demo src consists the file "clusterstore-cache-service.xml" and it is having the following code snippet for configuring TreeCache eviction policy.
<!-- 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">5000</attribute> <attribute name="timeToLiveSeconds">1000</attribute> </region> <!-- The Credit Verification query cache --> <region name="/CreditVerification"> <attribute name="maxNodes">1000</attribute> <attribute name="timeToLiveSeconds">5000</attribute> </region> </config> </attribute>
05:58:35,385 INFO [STDOUT] purchase for username1 05:58:35,405 INFO [STDOUT] Send mesg to ccproc 05:58:35,408 INFO [STDOUT] The Msg ID is ID:4-11728151154051 05:57:50,727 INFO [STDOUT] Finalized order called 05:57:50,728 WARN [TreeCache] node /CreditVerification not found 05:57:55,822 INFO [STDOUT] Finalized order called 05:57:55,823 WARN [TreeCache] node /CreditVerification not found 05:58:00,946 INFO [STDOUT] Finalized order called 05:58:00,947 WARN [TreeCache] node /CreditVerification not found 05:58:35,424 INFO [STDOUT] Finalized order called 05:58:35,425 WARN [TreeCache] node /CreditVerification not found
Do you know if there are any other caches running in the same app server, and perhaps trailblazer is talking to the wrong one? You can tell by looking in the JMX console.