Hide Forgot
Date of First Response: 2008-01-02 09:39:40 project_key: SOA See JBESB-1417
Link: Added: This issue depends JBESB-1417
Fixed on the CP branch. SHould be fixed with the next merge.
Kurt, I'm confused as to why you assigned this to me?
Link: Added: This issue related SOA-343
Link: Added: This issue related SOA-344
Link: Added: This issue related SOA-345
Cennot be verified due to SOA-344
Prevents issue testing
Link: Added: This issue depends SOA-344
Since the dependent issue is resolved in CR1, resolving this accordingly.
Verified in CR1
Seeing this line in SOA-P CR3: 19:52:36,403 INFO [EsbActionHandler] millisToWaitForResponse is no longer a valid element, please use a jBPM timer for this node instead. 19:52:35,786 WARN [ProxyWarnLog] Narrowing proxy to class org.jbpm.graph.node.StartState - this operation breaks == 19:52:35,802 INFO [STDOUT] Executed by the process, not by the ESB 19:52:36,010 INFO [STDOUT] 1********** Begin Service 1 *********** 19:52:36,012 INFO [STDOUT] In: Start It Up 19:52:36,013 INFO [STDOUT] Out: Service 1 Start It Up 19:52:36,013 INFO [STDOUT] ************ End Service 1 ************ 19:52:36,403 INFO [EsbActionHandler] millisToWaitForResponse is no longer a valid element, please use a jBPM timer for this node instead. 19:52:36,581 INFO [STDOUT] 2********** Begin Service 2 *********** 19:52:36,582 INFO [STDOUT] In: Service 1 Start It Up 19:52:36,582 INFO [STDOUT] Out: Service 2 Service 1 Start It Up 19:52:36,582 INFO [STDOUT] ************ End Service 2 ************ 19:52:36,975 INFO [STDOUT] 3********** Begin Service 3 *********** 19:52:36,976 INFO [STDOUT] In: Service 2 Service 1 Start It Up 19:52:36,976 INFO [STDOUT] Out: Service 3 Service 2 Service 1 Start It Up 19:52:36,976 INFO [STDOUT] ************ End Service 3 ************ 19:52:37,177 INFO [STDOUT] Executed by the process, not by the ESB 19:52:37,362 INFO [MessageSpy] Body: Service 3 Service 2 Service 1 Start It Up
removed millisToWaitForResponse statement
Verified in CP01