Isn't this related to eviction policy, as the EvictionTimerTask will be executed in a different thread? I thought Isolation Level REPEATABLE_READ will take care of dead-lock ! anonymous wrote : | at org.jboss.cache.TreeCache.evict(TreeCache.java:3716) | at org.jboss.cache.aop.PojoCache.evict(PojoCache.java:209) | at org.jboss.cache.eviction.BaseEvictionPolicy.evict(BaseEvictionPolicy.java:34) | at org.jboss.cache.eviction.BaseEvictionAlgorithm.evictCacheNode(BaseEvictionAlgorithm.java:210) | at org.jboss.cache.eviction.LRUAlgorithm.evict(LRUAlgorithm.java:90) | at org.jboss.cache.eviction.LRUAlgorithm.prune(LRUAlgorithm.java:121) | at org.jboss.cache.eviction.BaseEvictionAlgorithm.process(BaseEvictionAlgorithm.java:98) | at org.jboss.cache.eviction.EvictionTimerTask.run(EvictionTimerTask.java:80) | at java.util.TimerThread.mainLoop(Timer.java:512) | at java.util.TimerThread.run(Timer.java:462) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191823#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...