5:22 p.m.
[ http://jira.jboss.com/jira/browse/JBESB-993?page=comments#action_12375973 ]
Mark Kedzierski commented on JBESB-993:
---------------------------------------
I noticed a bug in the EsbActionHandler in the jbpm.esb module. (In the
jbossesb-jbpm.jar). When the action handler calls the ESB service, it does not store
the response message returned from the ESB service. The intention is to make a
synchronous call to the service (waiting x milliseconds for a response); then parse the
response message and insert it's data into JBPM context variables. But when the ESB
service invocation is made, the return value (Message) is ignored. It should be assigned
to the 'result' variable.
I noticed this when I wrote an orchestration process which passed the same dataset from
node-to-node for different stages of processing. The second node in the series would get
a null input, even though the first node outputed data.
The integrated jBPM works incorrectly - services invoked in random
pattern
--------------------------------------------------------------------------
Key: JBESB-993
URL: http://jira.jboss.com/jira/browse/JBESB-993
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.2
Reporter: Jiri Pechanec
Assigned To: Kevin Conner
Priority: Blocker
Fix For: 4.2.1
Try to run bpm_orchestration1. Check the log below. The process steps are executed
multiple times and there are error messages regarding token unlocking.
11:33:44,598 INFO [STDOUT] Executed by the process, not by the ESB
11:33:45,493 INFO [STDOUT] 1********** Begin Service 1 ***********
11:33:45,566 INFO [STDOUT] In: Start It Up
11:33:45,566 INFO [STDOUT] Out: Service 1 Start It Up
11:33:45,567 INFO [STDOUT] ************ End Service 1 ************
11:33:45,820 INFO [STDOUT] 2********** Begin Service 2 ***********
11:33:45,821 INFO [STDOUT] In: Service 1 Start It Up
11:33:45,821 INFO [STDOUT] Out: Service 2 Service 1 Start It Up
11:33:45,821 INFO [STDOUT] ************ End Service 2 ************
11:33:46,868 INFO [STDOUT] 3********** Begin Service 3 ***********
11:33:46,868 INFO [STDOUT] In: Service 2 Service 1 Start It Up
11:33:46,869 INFO [STDOUT] Out: Service 3 Service 2 Service 1 Start It Up
11:33:46,869 INFO [STDOUT] ************ End Service 3 ************
11:33:47,615 INFO [STDOUT] Executed by the process, not by the ESB
11:33:47,742 INFO [MessageSpy] Body: Service 3 Service 2 Service 1 Start It Up
11:33:48,631 WARN [Token] lock owner 'token[1]' tries to unlock token
'1' which is not locked
11:33:48,631 INFO [STDOUT] Executed by the process, not by the ESB
11:33:48,773 INFO [MessageSpy] Body: Service 3 Service 2 Service 1 Start It Up
11:33:49,611 WARN [Token] lock owner 'token[1]' tries to unlock token
'1' which is not locked
11:33:49,715 INFO [STDOUT] 3********** Begin Service 3 ***********
11:33:49,716 INFO [STDOUT] In: Service 3 Service 2 Service 1 Start It Up
11:33:49,716 INFO [STDOUT] Out: Service 3 Service 3 Service 2 Service 1 Start It Up
11:33:49,716 INFO [STDOUT] ************ End Service 3 ************
11:33:50,568 INFO [STDOUT] Executed by the process, not by the ESB
11:33:50,753 INFO [MessageSpy] Body: Service 3 Service 3 Service 2 Service 1 Start It
Up
11:33:51,586 WARN [Token] lock owner 'token[1]' tries to unlock token
'1' which is not locked
11:33:51,587 INFO [STDOUT] Executed by the process, not by the ESB
11:33:51,681 INFO [MessageSpy] Body: Service 3 Service 3 Service 2 Service 1 Start It
Up
11:33:52,542 WARN [Token] lock owner 'token[1]' tries to unlock token
'1' which is not locked
11:33:52,638 INFO [STDOUT] 2********** Begin Service 2 ***********
11:33:52,638 INFO [STDOUT] In: Service 3 Service 3 Service 2 Service 1 Start It Up
11:33:52,659 INFO [STDOUT] Out: Service 2 Service 3 Service 3 Service 2 Service 1 Start
It Up
11:33:52,659 INFO [STDOUT] ************ End Service 2 ************
11:33:53,652 INFO [STDOUT] 3********** Begin Service 3 ***********
11:33:53,653 INFO [STDOUT] In: Service 2 Service 3 Service 3 Service 2 Service 1 Start
It Up
11:33:53,653 INFO [STDOUT] Out: Service 3 Service 2 Service 3 Service 3 Service 2
Service 1 Start It Up
11:33:53,653 INFO [STDOUT] ************ End Service 3 ************
11:33:54,436 INFO [STDOUT] Executed by the process, not by the ESB
11:33:54,507 INFO [MessageSpy] Body: Service 3 Service 2 Service 3 Service 3 Service 2
Service 1 Start It Up
11:33:55,383 WARN [Token] lock owner 'token[1]' tries to unlock token
'1' which is not locked
11:33:55,384 INFO [STDOUT] Executed by the process, not by the ESB
11:33:55,472 INFO [MessageSpy] Body: Service 3 Service 2 Service 3 Service 3 Service 2
Service 1 Start It Up
11:33:56,343 WARN [Token] lock owner 'token[1]' tries to unlock token
'1' which is not locked
11:33:56,519 INFO [STDOUT] 3********** Begin Service 3 ***********
11:33:56,519 INFO [STDOUT] In: Service 3 Service 2 Service 3 Service 3 Service 2 Service
1 Start It Up
11:33:56,520 INFO [STDOUT] Out: Service 3 Service 3 Service 2 Service 3 Service 3
Service 2 Service 1 Start It Up
11:33:56,520 INFO [STDOUT] ************ End Service 3 ************
11:33:57,307 INFO [STDOUT] Executed by the process, not by the ESB
11:33:57,352 INFO [MessageSpy] Body: Service 3 Service 3 Service 2 Service 3 Service 3
Service 2 Service 1 Start It Up
11:33:58,256 WARN [Token] lock owner 'token[1]' tries to unlock token
'1' which is not locked
11:33:58,256 INFO [STDOUT] Executed by the process, not by the ESB
11:33:58,385 INFO [MessageSpy] Body: Service 3 Service 3 Service 2 Service 3 Service 3
Service 2 Service 1 Start It Up
11:34:00,073 INFO [MessageSpy] Body: Service 3 Service 3 Service 2 Service 3 Service 3
Service 2 Service 1 Start It Up
--
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