[
http://jira.jboss.com/jira/browse/JBESB-708?page=all ]
Kevin Conner closed JBESB-708.
------------------------------
Resolution: Done
Checked in in revision 13571.
There was a missing process-definition-name property for the second action and the name
used was incorrect. bpm_orchestration2 was also missing the property.
Error running bpm_orchestration1
--------------------------------
Key: JBESB-708
URL:
http://jira.jboss.com/jira/browse/JBESB-708
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Examples
Affects Versions: 4.2 Milestone Release 2
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2 Milestone Release 3
bpm_orchestration1 fails to run the process. The BpmProcessor action fails with the
following error message.
12:37:01,670 ERROR [STDERR] java.lang.Exception: Either <jbpmTokenId> or
<jbpmProcessInstId> object must be specified in Message body to know who to signal
12:37:01,670 ERROR [STDERR] at
org.jboss.soa.esb.services.jbpm.actions.impl.DefaultCommandExecutorFactoryImpl$8.execute(DefaultCommandExecutorFactoryImpl.java:270)
12:37:01,670 ERROR [STDERR] at
org.jboss.soa.esb.services.jbpm.actions.CommandInterpreter.process(CommandInterpreter.java:78)
12:37:01,670 ERROR [STDERR] at
org.jboss.soa.esb.services.jbpm.actions.BpmProcessor.process(BpmProcessor.java:64)
--
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