Hi, sorry for the late response. 1) Red Hat does offer paid support for JBoss Cache as a part of the JBoss EAP subscription. 2) Interesting that using the dummy TM solves the problem - it is still a real TM capable of holding real locks. It's just that other components in the app server won't be using it as well. Perhaps there is some contention there. 3) jmxStats: could you please create a JIRA for this, and preferably attach a simple unit test? 4) Eviction: the general solution here is to either reduce the wakeup interval (JBC 3 uses millis to measure this so you can go under 1s if needed) or increase the eviction queue size. This may well be why your readers are hanging. Cheers Manik View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248479#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...