[
https://issues.apache.org/jira/browse/OPENJPA-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-2198.
--------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: The report is two lines against
1.0.x with no entity, query or stack trace. Locking has since been reworked
around JPA 2 lock modes (MixedLockManager/PessimisticLockManager in
openjpa-jdbc/.../jdbc/kernel), so nothing can be checked against master. Please
reopen if this still happens with OpenJPA 4.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
> Priority: Major
> 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 was sent by Atlassian Jira
(v10.3.26#10030026)
