openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abe White (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-203) Pessimistic Lock Manager not locking the rows
Date Thu, 05 Apr 2007 19:15:32 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487078
] 

Abe White commented on OPENJPA-203:
-----------------------------------

If we don't want the subclasses to have to unset the lock value in case of exception, another
option would be to have lock() delegate to lockInternal for setting the lock value, but to
unset the lock value itself on error:

int oldValue = getLockValue(sm);
try {
    lockInternal(...);
} catch (RuntimeException re) {
    setLockValue(sm, oldValue);
    throw re;
}

> Pessimistic Lock Manager not locking the rows 
> ----------------------------------------------
>
>                 Key: OPENJPA-203
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-203
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 0.9.0, 0.9.6
>         Environment: ran against Oracle
>            Reporter: Srinivasa
>         Attachments: NotesAndDiff.txt, testcase.zip
>
>
> With  pessimistic lock manager multiple EMs are able to modify the same object concurrently.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message