Exception: org.hibernate.exception.ConstraintViolationException: could not execute JDBC batch update

I have a composition of entities A composing B composing C . When I use camel-jpa/hibernate in a single thread they go in fine but when I use mutiple threads I get the exception in the subject.

I think the cause is hibernate is generating insert statements as opposed to update statements

and

putting them in the same JDBC update.

Question is how do I force camel-JPA/Hibernate to always lock the table do a clean select for the primary key before generating those statements so this way it would always force to do a select before generating an update ?

Hi,


I really don't think that's the cause.

I suggest you as first step to disable jdbc-batching for the moment by specifying

this should give you more clear exception messages when jdbc-exceptions raise.

Then please report the exception again with complete message and full-stacktrace.
Usually (it depends on the undelying database and driver) there's also written which Constraint was violated.
Furthermore I suggest you to log all the jdbc-statements with p6spy.
Knowing the last jdbc-statement before the ConstraintViolationException raises and knowing which constraint is getting violated,
should help you to understand what's going wrong.