Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <4773868.240091281383055873.JavaMail.jira@thor>
Date: Mon, 9 Aug 2010 15:44:15 -0400 (EDT)
From: "Rick Curtis (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Created: (OPENJPA-1762) javax.persistence.lock.scope
 EXTENDED doesn't properly lock join tables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

javax.persistence.lock.scope EXTENDED doesn't properly lock join tables
-----------------------------------------------------------------------

                 Key: OPENJPA-1762
                 URL: https://issues.apache.org/jira/browse/OPENJPA-1762
             Project: OpenJPA
          Issue Type: Bug
          Components: jdbc
    Affects Versions: 2.0.1, 2.1.0
         Environment: Derby and DB2
            Reporter: Rick Curtis
         Attachments: OPENJPA-1762.PATCH

I have a simple failing unit test that exercises a small portion of the javax.persistence.lock.scope=Extended property. The failing scenario is as follows:

ManyToMany relationship between A(owner) and B.

Em1 - Find A, no lock
Em1 - Refresh A, PESSIMISTIC_FORCE_INCREMENT and javax.persistence.lock.scope=PessimisticLockScope.EXTENDED -- this SHOULD lock the join table for A_B
Em2 - Find, lock B. Remove B.  should block while trying to remove from Join table.

I will post the unit test which demonstrates the problem shortly.

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