> Be sure your sequences are synchronized before the start of Sequoia.
It seems that I have had used a "corrupt" dump as basis for testing.
After all the testing the sequence-value for table "qscategories"
disaligned to the real record-count of the table (table row count was
greater than actual sequence-value).
Following this circumstance it is correct, that jboss throws a
javax.ejb.DuplicateKeyException, because jboss always double-checks the
sequence-value it is getting from db, first getting the sequence-value
and then making a select on the table to check, if this sequence-value
is already used:
17:30:03,162 qualiproof-dev S 3918 1006 {call
nextval('SEQ_QSCATEGORIES)}
17:30:03,217 qualiproof-dev S 3919 1006 SELECT COUNT(*) FROM
qscategories WHERE ID=?/<!%L|250183|!%>
After installing cluster from a clean corrected dump, all is now ok.
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
