OK. If it's the same server, then a locally running transaction is still active when you redeploy the ear. The timeout can help. Also suggest you have a look at how things are packaged; i.e. where the clients are that are using the cache, why they are still alive when EJB3 is trying to undeploy the entity. That could be a packaging problem on your side or it may indicate a problem in the dependency management within EJB3. Any info you can give on that would be appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108949#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...