BPM lock with ESB_ASYNC_SIGNAL_ACTION

[paradigmza]

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.

[kconner]

They are, in essence, single threaded for the signal being executed but it sounds as if there is a bug somewhere.

What type of error are you seeing?

My guess would be that the unlock of the token has been rolled back by the transaction and the token will therefore need to be explicitly unlocked before it can be used.

Can you create a JIRA for this and attach an example of the failure?

Thanks,

Kev

[paradigmza]

Yes, I had a quick look into it. I call an EJB which must join the transaction, this EJB then throws a RuntimeException which would then rollback. I will create a Jira.

[kconner]

Great, thanks very much.