[jira] Updated: (OPENJPA-1765) TableGenerator doesn't properly utilize all keys when under heavy stress.

["Michael Dick (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OPENJPA-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dick updated OPENJPA-1765:
----------------------------------

    Fix Version/s: 2.0.2

> 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, 2.1.0
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>             Fix For: 2.0.2, 2.1.0
>
>         Attachments: OPENJPA-1765.patch
>
>
> 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.