[
https://issues.apache.org/jira/browse/OPENJPA-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-639.
-------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: This is an idle 2008 wish with no
design. JPA pessimistic locking (MixedLockManager) now covers the use case of
avoiding commit-time failures. Please reopen if this still happens with OpenJPA
4.x.
> A PersistenceUnit/JVM -wide in-memory Lock manager for optimistic transaction
> -----------------------------------------------------------------------------
>
> Key: OPENJPA-639
> URL: https://issues.apache.org/jira/browse/OPENJPA-639
> Project: OpenJPA
> Issue Type: Wish
> Reporter: Pinaki Poddar
> Priority: Major
>
> Under optimistic transaction model, OpenJPA detects lock violations a) by
> checking version stamps b) at commit time.
> It is non-trivial to recover from a failure detected at commit time. Hence
> the proposal is for a lock manager that obtains in-memory locks on object.
> A combination of
> a) Lock objects in Java 5 and
> b) a capability to find other instances that represent the same database
> record within i) the same JVM or ii) in the same persistent unit
> can be a good starting point for such a feature.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
