Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <17465679.310831281637455821.JavaMail.jira@thor>
Date: Thu, 12 Aug 2010 14:24:15 -0400 (EDT)
From: "Rick Curtis (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Created: (OPENJPA-1765) TableGenerator doesn't properly
 utilize all keys when under heavy stress.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

TableGenerator doesn't properly utilize all keys when under heavy stress.
-------------------------------------------------------------------------

                 Key: OPENJPA-1765
                 URL: https://issues.apache.org/jira/browse/OPENJPA-1765
             Project: OpenJPA
          Issue Type: Bug
          Components: jdbc
    Affects Versions: 2.0.0
            Reporter: Rick Curtis
            Assignee: Rick Curtis


TableJDBCSeq has a locking problem where multiple threads can run on top of each other resulting in all keys not being used for a given sequence. 

While unit testing a fix I also uncovered another theoretical start up problem where multiple threads can try to insert the same row into the DB resulting in a duplicate key exception.

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