[jboss-user] [jBPM] - jBPM- Transaction isolation level

Maurice de Chateau do-not-reply at jboss.com
Thu May 6 10:41:01 EDT 2010

Maurice de Chateau [http://community.jboss.org/people/MohReece] replied to the discussion

"jBPM- Transaction isolation level"

To view the discussion, visit: http://community.jboss.org/message/541577#541577

Hi Alexander,

You're not mentioning which version of jBPM you're using, but in the user guide for version 3.2.x ( http://docs.jboss.com/jbpm/v3.2/userguide/html/persistence.html#isolationlevelofthejdbcconnection http://docs.jboss.com/jbpm/v3.2/userguide/html/persistence.html#isolationlevelofthejdbcconnection) you can read the following:

"+Make sure that the database isolation level that you configure for  your        JDBC connection is at least READ_COMMITTED.+
+Almost all features run OK even with READ_UNCOMMITTED  (isolation level 0       and the only isolation level supported by HSQLDB).  But race  conditions might occur in the        job executor and with synchronizing multiple tokens.+"

So that's quite clear in itself. But if you want a little more background, you can read this JIRA issue ( *https://jira.jboss.org/jira/browse/JBPM-983 JBPM-983*), in which Tom Baeyens explains about the underlying reasoning for this persistence aspect.



Reply to this message by going to Community

Start a new discussion in jBPM at Community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20100506/29155283/attachment.html 

More information about the jboss-user mailing list