[ https://issues.apache.org/jira/browse/OPENJPA-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278365#comment-13278365 ]
Heath Thomann commented on OPENJPA-2198: ---------------------------------------- The fix for this issues seemed to have sneaked into 1.1.x+. See here: http://openjpa.markmail.org/search/?q=AbstractVersionStrategy.checkVersion#query:AbstractVersionStrategy.checkVersion+page:1+mid:x4rcoh72qegaaysm+state:results As such, the issue currently only resides on 1.0.x and this JIRA will be used to fix the issue on 1.0.x. > Query return OptimisticLockExceptions when openjpa.Optimistic is turned off > --------------------------------------------------------------------------- > > Key: OPENJPA-2198 > URL: https://issues.apache.org/jira/browse/OPENJPA-2198 > Project: OpenJPA > Issue Type: Bug > Components: jpa > Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4 > Reporter: Helen Xu > Assignee: Helen Xu > Attachments: OPENJPA_2198Patch > > > User has the following lock setting > <property name="openjpa.jdbc.TransactionIsolation" value="repeatable-read"/> > <property name="openjpa.Optimistic" value="false"/> > Running a query returned OptimisticLockExceptions -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira