[ https://issues.apache.org/jira/browse/OPENJPA-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pinaki Poddar reopened OPENJPA-466: ----------------------------------- The issue of sequence value creation under multithreaded environment is still relevant. I ran a very simple tests that do the following 1. A entity with @GeneratedValue primary key 2. 4 threads that persist() entities in separate persistence contexts The test breaks with OPENJPA_SEQUENCE_TABLE being populated with duplicate key -- looks like a concurrency issue. > Primary key constraint violated using (Oracle) sequence to generate ID in > multithreaded app > ------------------------------------------------------------------------------------------- > > Key: OPENJPA-466 > URL: https://issues.apache.org/jira/browse/OPENJPA-466 > Project: OpenJPA > Issue Type: Bug > Affects Versions: 1.0.0, 1.0.1, 1.1.0, 1.2.0 > Environment: OpenJPA 1.0.0 (also tried 1.0.1 and 1.1.0-SNAPSHOT) > Oracle XE 10g (JDBC driver 10.2.0.3.0) > Windows XP Pro > Reporter: Frank Le > Assignee: Milosz Tylenda > Priority: Blocker > Fix For: 1.0.4, 1.2.2, 1.3.0, 2.0.0-M3 > > Attachments: OPENJPA-466-1.0.x.patch, OPENJPA-466-1.2.x.patch, > OPENJPA-466-SYNCRONIZED.patch, OPENJPA-466.patch, OPENJPA-466.patch, > volatile.patch > > > Here's how I annotate the ID: > @Id > @SequenceGenerator(name = "FooSeq", sequenceName = "seq_foo", > allocationSize = 20) > @GeneratedValue(strategy = GenerationType.SEQUENCE, generator = "FooSeq") > private Long id; > Here's how I create the (Oracle) sequence: > CREATE SEQUENCE seq_foo START WITH 1 INCREMENT BY 1; > I get a primary key unique constraint violated in a multithreaded app i.e. it > doesn't happen in single-threaded! > You can simply reproduce this error by either create blocking queue or > blocking thread pool say size 5 to insert 10000+ object. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.