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 15:11:32 GMT

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

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

Looks good.  Although I think I'd prefer to make lockInternal() responsible for setting the
lock level rather than having to set it and unset it so that lock() can set it again... it's
just too ugly.  So instead we just remove the setting of the lock level in lock() and make
VersionLockManager only unset the lock level in its lockInternal if an exception occurs. 
PessimisticLockManager wouldn't have to change (outside of the changes already in your patch)
because it delegates to super.lockInternal already, so the lock level would get set appropriately.
 

> 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