[OPENJPA-1765] TableGenerator doesn't properly utilize all keys when under heavy stress.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0, 2.1.0
• Fix Version/s: 2.0.2, 2.1.0
• Component/s: jdbc
• Assignee: Richard G. Curtis
• Reporter: Richard G. Curtis
• Created: 12/Aug/10 18:23
• Updated: 09/Nov/10 14:59
• Resolved: 13/Sep/10 21:58

Description

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.

Issue Links

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