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.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|32d 3h 35m||1||Rick Curtis||13/Sep/10 21:58|
|56d 17h||1||Rick Curtis||09/Nov/10 14:59|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||2.0.2 [ 12315257 ]|
|Fix Version/s||2.1.0 [ 12314542 ]|
|Affects Version/s||2.1.0 [ 12314542 ]|