Should i download whole AS? Can you please provide a path to appropriate repo? I'd be gratefull.

Hi there,

I did what you told me, but it didn't solved my problem.
ant dist went ok (with some warnings ), but the 'ant deploy' task failed with "cannot find JMS provider".
I tried to deploy my esb to new server instance (in product\build\jbossesb-server-4.4.GA) and it worked. So, i changed deploy.properties in my project, deployed it and started. Here's what went wrong:

org.jbpm.JbpmException: couldn't execute org.jboss.soa.esb.services.jbpm.cmd.CommandExecutor$AsyncStartProcessInstanceCommand@7d29df
at org.jboss.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:73)

I found that the original exception thrown from AsyncStartProcessCommand says that:

'org.jbpm.JbpmException: can't create a process instance when processDefinition is null"

Any ideas?

ok, i'm sorry for this - i've forgot to deploy the process :\
The error i've claimed to solve doesn't show now, but i still can't get response to go.
Question for now is: where exactly should i wait for reply ? in X_reply queue? (where queue X is the origin process initiator queue) When i synchronously get a response from service starting process (by ServiceInvoker.deliverSync()) the response is a message from before the process (and, in fact, i get the reply before the process ends).

I'm glad i have no exceptions, but it's not enough :)

Thanks,
Piotrek

Hi there!

Thanks for your reply.
As far as i know, storing replyTo field in message isn't obligatory - when there's no such field, queueName_reply is used. The thing is this queue (reply) is defined, but i get reply even before the process ends..

i'm afraid it's not working.
I've set mep=OneWay on the service wich starts the process, and with mappings and replyToOriginator property set as a last action of a last node of a process, or as an action of end state(the results are equal).
What i get is JBoss tries to run process twice ( i don't know why) - it runs correctly, but i get unresponsive EPR on every try (on the queue from wich process was started). Then i see a "Delivering message" to the same queue. After that i get an exception (MessageDeliverException) telling me that it can't deliver a message to my bpmStarter service (in fact it correctly points this service's _reply queue).

Thanks,
Piotrek

Thank you very much for your willing to help.

Here is my piece of jboss-esb.xml:

<service category="BPM" name="BPMStarter"
 description="BPM Orchestration Sample 1: Use this service to start a process instance">
 <listeners>
 <jms-listener name="Gateway" busidref="testingFirstjBPMGwChannelNew"
 is-gateway="true" />
 <jms-listener name="ESB-Listener" busidref="testingSecondjBPMEsbChannelNew"/>
 </listeners>
 <actions mep="OneWay">
 <action name="create_new_process_instance"
 class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor">
 <property name="command" value="StartProcessInstanceCommand" />
 <property name="reply-to-originator" value="true"/>
 <property name="process-definition-name" value="testBPM"/>
 <property name="esbToBpmVars">
 <mapping esb="payload" bpm="theBody" />
 </property>
 </action>
 </actions>
 </service>

<?xml version="1.0" encoding="UTF-8"?>

<process-definition xmlns="" name="testBPM">
 <start-state name="firstJBPM">
 <transition to="someService"></transition>
 </start-state>
 <node name="someService">
 <action class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler">
 <esbServiceName>
 testingResponseNew
 </esbServiceName>
 <esbCategoryName>
 testowe
 </esbCategoryName>
 <bpmToEsbVars>
 <mapping bpm="theBody" esb="payload" />
 </bpmToEsbVars>
 <esbToBpmVars>
 <mapping bpm="theBody" esb="payload" />
 </esbToBpmVars>
 </action>
 <transition to="someService2"></transition>
 </node>
 <node name="someService2">
 <action class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler">
 <esbServiceName>
 testingResponseNew
 </esbServiceName>
 <esbCategoryName>
 testowe
 </esbCategoryName>
 <bpmToEsbVars>
 <mapping bpm="theBody" esb="payload" />
 </bpmToEsbVars>
 <esbToBpmVars>
 <mapping bpm="theBody" esb="payload" />
 </esbToBpmVars>
 </action>
 <transition to="end-state1"></transition>
 </node>
 <end-state name="end-state1">
 <action class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbNotifier">
 <property name="reply-to-originator" value="true"/>
 <replyToOriginator>true</replyToOriginator>
 <bpmToEsbVars>
 <mapping bpm="theBody" esb="payload" />
 </bpmToEsbVars>
 <esbToBpmVars>
 <mapping bpm="theBody" esb="payload" />
 </esbToBpmVars>
 </action>
 </end-state>
</process-definition>

System.setProperty("javax.xml.registry.ConnectionFactoryClass","org.apache.ws.scout.registry.ConnectionFactoryImpl");

 ServiceInvoker invoker = new ServiceInvoker(this.getTargetCategory(), this.getTargetService());
 Message requestMessage = MessageFactory.getInstance().getMessage(MessageType.JBOSS_XML);
 requestMessage.getBody().add(PAYLOAD_NAME,msg);

 Message replyMessage = invoker.deliverSync(requestMessage, 6000);

The change of replyToOriginator didn't made any difference - the exception still occurs. The bigger wait time let the process to run not 2, but 4 times ( each time the unresponsive EPR took place).