[esb-issues] [JBoss JIRA] Commented: (JBESB-1443) CallbackCommand state checker can fail in case of loops in BPM process
[ http://jira.jboss.com/jira/browse/JBESB-1443?page=comments#action_12393956 ]
Kevin Conner commented on JBESB-1443:
-------------------------------------
Looping is not the issue as the counter will handle this, however different threads of
control are.
The variable should have been named using the node id *and* the token id to differentiate
between different process threads of control.
CallbackCommand state checker can fail in case of loops in BPM
process
----------------------------------------------------------------------
Key: JBESB-1443
URL: http://jira.jboss.com/jira/browse/JBESB-1443
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kurt Stam
Priority: Critical
Fix For: 4.2.1 CP1
If there is a loop in jBPM process (or more precisely if the same node is invoked more
than once) then the CallbackCommand checking of state can fail.
The problem is that checking is based on processId and nodeId. But this combination is
not unique if the same node is invoked more than once.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira