This occurs only in jbpm 4.3, but is not in jbpm 4.2. Check the source code, beleive it is a change in java file ExecutionImpl.java, about on line 380 caused this. See code snippet below, left side is the code in 4.3.