[jboss-user] [JBoss jBPM] - Re: Problem with a decision node in a fork, join construct.

[kukeltje]

hhhhhhhhhhhmmmmmmmmmmmm............. Martin, you are great. Your memory works better than mine ;-) 

So it was no deja-vu, but a real memory....

Jan, so it is a regression. Could you try and the flush to the join node, (re) compile jbpm (or that one class) and test? 

  | Index: modules/core/src/main/java/org/jbpm/graph/node/Join.java
  | ===================================================================
  | --- modules/core/src/main/java/org/jbpm/graph/node/Join.java	(revision 3339)
  | +++ modules/core/src/main/java/org/jbpm/graph/node/Join.java	(working copy)
  | @@ -123,7 +123,9 @@
  |            // force version increment by default (LockMode.FORCE)
  |            LockMode lockMode = parentLockMode != null ? LockMode.parse(parentLockMode) : LockMode.FORCE;
  |            log.debug("acquiring " + lockMode + " lock on " + parentToken);
  | -          // lock updates as appropriate, no need to flush here
  | +          // Required for Oracle, see https://jira.jboss.org/jira/browse/JBPM-1085
  | +          session.flush();
  | +          // lock updates as appropriate
  |            session.lock(parentToken, lockMode);
  |          }
  |  
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4196531#4196531

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4196531