3 Replies Latest reply on May 12, 2009 4:43 AM by Kevin Conner

    BPM lock with ESB_ASYNC_SIGNAL_ACTION

    Sean Burns Newbie

      Hello I setup a ESB action to call a BPM process

      <actions mep="OneWay">
       <action class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor"
       name="Invoke BPM Process">
       <property name="command" value="StartProcessInstanceCommand" />
       <property name="process-definition-name" value="Test SMS" />
       <property name="esbToBpmVars">
       <mapping bpm="fromCellNumber" esb="body.smsData-fromCellNumber" />
       <mapping bpm="smsContents" esb="body.smsData-contents" />
       </property>
       </action>
       </actions>


      This works as expected, but when there is an exception in the process (so it is stuck on some state/node). All new messages invoke the the process, but do not start (just wait on the starting node).

      When I try to manually trigger the new tokens to move to the next node (via jbpm-console) I get an error that says it is locked by "ESB_ASYNC_SIGNAL_ACTION".

      Does this mean that all invocation on a process via ESB are essentially "single threaded", and new message wont be processed until the last is completed?

      And, is there a work around for this?

      Thanks
      Sean.