[jboss-user] [jBPM] New message: "Re: jbpm 4.3 - org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update"

Ronald van Kuijk do-not-reply at jboss.com
Wed Jan 27 15:23:30 EST 2010

User development,

A new message was posted in the thread "jbpm 4.3 - org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update":


Author  : Ronald van Kuijk
Profile : http://community.jboss.org/people/kukeltje

Let me first clear some things up. This forum does not get silent when transactions are mentioned, it just does not get active. Keep in mind that this is a user forum. User forum in more sense then one. It is for users, by users. So it is a peer forum. If you run a less commonly used application server (WLS 11g), there is a bigger chance of not getting help. I myself used WLS up to 8.1SP4 (or was it 5) so have no options to even try to help out and suggesting things. So I keep quiet to. This is probably true for many other users as well. (using db2 is comparable as there are also less people using it, at least as WLS in combination with jBPM)
Secondly, as long as there is no *minimal* testcase where things can be reproduced on the (currently) supported configurations (supported in the sense that there is qa cycle for it, not that it will only run on these), it is even harder to start helping out.
What I further get from this topic is that I hear things like table locking... that is scary
Further more, if things seem related to 'async', (dead) locks etc, read http://docs.jboss.com/jbpm/v4/userguide/html_single/#asynchronouscontinuations again and pay special attention to the third possible value of the continue attribute, called exclusive.... Maybe it helps...


To reply to this message visit the message page: http://community.jboss.org/message/522625#522625

More information about the jboss-user mailing list