"bstansberry(a)jboss.com" wrote : JBoss Cache doesn't suspend/resume the transaction; it's Hibernate's integration with JBC that does this. If JBC sees an active transaction it will hold a lock on data in the cache until that tx commits. There are times when it's incorrect for those locks to be held for that long, so Hibernate suspends the tx before calling into JBC. Suspend/resume is invoked from org.jboss.cache.interceptors.InvocationContextInterceptor#handleAll while optionOverride.isFailSilently() returns true. It comes from org.jboss.cache.invocation.CacheInvocationDelegate#putForExternalRead. Maybe you meant that suspent/resume is invoked by Hibernate which invoked JBC methods with appropriate parameters. As regards your suggestions: 1) I don't use query cache 2) Problem occures in read only transaction 3) Any evict on org.hibernate.SesssionFactory and org.hibernate.cache.CacheConcurrencyStrategy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4263152#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...