[OPENJPA-1372] Generating identifiers by using sequence table may fail during sequence table initialization

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.1, 2.0.0-M3
• Fix Version/s: 2.0.2, 2.1.0
• Component/s: jdbc, kernel
• Assignee: Michael Dick
• Reporter: Milosz Tylenda
• Created: 31/Oct/09 21:26
• Updated: 30/Sep/12 20:58
• Resolved: 07/Sep/10 22:49

Description

When sequence table does not exist and mutliple threads get EntityManagers from EntityManageFactory, an insert into sequence table may fail because of duplicate primary key value.

EMF is created lazily by default and users reported various problems with concurrent initialization (e.g. failures in resolving aliases in JPQL queries, IIRC) of EMF. This issue might have the same roots.

Issue and test case originally reported by Pinaki in OPENJPA-466.

Issue Links

• is related to: OPENJPA-1765 TableGenerator doesn't properly utilize all keys when under heavy stress.
• relates to: OPENJPA-466 Primary key constraint violated using (Oracle) sequence to generate ID in multithreaded app
• relates to: OPENJPA-2269 Duplicate key exception in sequence table on multithreaded initialization