Indeed it has to do with the subprocess which signals the parent process in the current implementation, and did not do that in the previous implementation.
In our case we have a process with a root token and some child tokens. The child tokens have a sub process.
When ending a child token, it should stop directly.
Now when we call childToken#end(false), subProcessInstance#end() will be called. This will reactivate the super token which we don't want.
Before childToken#end(false), called subProcessInstance#end(false) which did not reactivate the super token...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200526#4200526
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200526
Hmmmmm ProcessInstance#end(boolean reactivateSuper) sounds a bit weird to me... So I can imagine it was removed. Can you describe the usecase for this? Does it have something to do with subprocesses which you want to end but not have it signal the parent process?
What if you woud do change
anonymous wrote : processInstance.end(false)
to
anonymous wrote : processInstance.getRootToken().end(false)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200525#4200525
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200525
Just FYI (normally I hate these ' I have the same problem' reports without any additional information), I have the same problem with jBPM (3.3.1.GA), MySQL 5.0.67, MySQL Connector 5.1.6, openJDK 6, with the XA configuration that comes with jBPM. If I go back to a non-xa config it works. I (but that is really personal) refuse from now on to use HSQLDB.
Currently have no time to verify this, but feel free to file a jira issue for this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200523#4200523
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200523