anonymous wrote : | | Now, the second load request gets processed. So Hibernate checks the cache to see if the data exists there. However, we have previously acquired a write lock in the other session so this process is blocked until that write lock is released when the first session ends its transaction. | | I thought you use the fail silently Option when interacting with the cache? This will prevent the cache from participating in any ongoing tx so the write lock will only exist for the duration of the cache.put() method call, not the entire transaction. Agreed about a read-lock-only option when calling a put though, this will helpimprove concurrency a good deal more. Curious, how do the likes of EHCache, etc. deal with this? I don't believe they have 2 different put() methods... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966626#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...