|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Found it ! Validation errors are causing the transaction to be rolled back alright.
But for an obscure reason in OUR code a flush takes place in a finally{} block. Regardless the transaction's state.
I presume flushing while the transaction is meant to be rolled back causes an inconsistent state of some kind. Finally degrading into a primary key violation. In 4.1.7 however the validation error comes through. As of 4.1.8 the PK violation shows.
The bottom line however is that this is not a bug. Mea Culpa.
Is there any way to close this ticket ?