[
https://issues.apache.org/jira/browse/OPENJPA-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899132#action_12899132
]
Michael Dick commented on OPENJPA-1765:
---------------------------------------
Looks similar, but I think it's different. Can OPENJPA-1372 be reproduced
without sharing the EM between threads?
The added locking in this fix will prevent two EMs from getting the same
sequences, I'm not sure about a single thread using the same EM. Might be worth
running the test from 1372 to see if it still fails.
> 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.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.
