Please check the following links that may help you solve the problem.
https://issues.apache.org/jira/browse/OPENJPA-1192 https://issues.apache.org/jira/browse/OPENJPA-381 First, if users use JPA "out of the box" in WebSphere, they might think that they are getting optimistic locking by default -- but in fact they are not. The reason is the default isolation level on a data source in Websphere is REPEATABLE READ. This gives pessimistic, not optimistic locking. Optimistic locking defines that locks are not held on data that is read by the application -- View this message in context: http://openjpa.208410.n2.nabble.com/distributed-transaction-waiting-for-lock-tp5997733p6006828.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
