"ALRubinger" wrote : https://jira.jboss.org/jira/browse/EJBTHREE-1549 I've committed tests and a fix for this issue. r80096 will show that instead of holding the cacheMap's intrinsic lock throughout passivation, we now just make a copy of the Map's contents, then free the lock before running passivation. Side effect: Perhaps removal task might sneak in there and remove an instance before passivation can come along. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184734#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...