If there is no eviction policy, then regardless of the cache loader configuration, all the cache data is kept in memory. Now, the data might fail to be stored using a put().
I would suggest creating a separate log4j appender that captures all the debug logs for org.jboss.cache, that rolls over (so you don't fill your disk). Then, when you receive back a null, alert your operator, or automatically turn off debug. (This can be done using calls to the log4j API.) You should be able to see what's happening then. Perhaps it's your application. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4058330#4058330 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4058330 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
