[OPENJPA-466] Primary key constraint violated using (Oracle) sequence to generate ID in multithreaded app

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.0.0, 1.0.1, 1.1.0, 1.2.0
• Fix Version/s: 1.0.4, 1.2.2, 1.3.0, 2.0.0-M3
• 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
• Patch Info: Patch Available
• Assignee: Milosz Tylenda
• Reporter: Frank Le
• Created: 13/Dec/07 02:40
• Updated: 09/Mar/10 18:31
• Resolved: 31/Oct/09 21:13

Description

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.

Issue Links

• is related to: OPENJPA-1372 Generating identifiers by using sequence table may fail during sequence table initialization