Thanks for the reply. I have the same concern regarding the deprecated pessimistic locking. The JBC documents keeps talking about the benefit of mvcc, but failed to address this common use case. Note that the concurrent write is not really an exception in this scenario, it is expected to happen frequently, and need to be handled in a way that guarantees the continuation of the application logic (i.e., no starvation, the write will be executed in a finite time without hurting data integrity). Anyone else having the same issue? Any other ideas? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256469#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...