"andreskusa" wrote : So, even if you stay inside jBPM/ESB (i.e., if jBPM starts a service that immediately calls the BpmCallback action) you need to copy the replyTo-EPR to the To-EPR. &quot;Kevin.Conner(a)jboss.com&quot; wrote : | But jBPM should not be invoking the reply service, it should be invoking another service which then sends its reply to the callback service. The processing of a RequestResponse mep in the pipeline will send a response to the ReplyTo EPR and, in this way, we are no different from specs such as WS-Addressing. | No, sorry, the way I meant it was the way you described it: I did not start the bpmCallback-Service from jBPM, but rather started an ESB service (via EsbActionHandler) which directly called the action org.jboss.soa.esb.services.jbpm.actions.JBpmCallback. This is what I mean with "inside" in comparison to what I described by the correlation of internal EPR and external services. So, since I "leave" the ESB I have to create a new EPR anyway and it doesn't matter for me so much now that I need to call an action which fills my to-Object in the EPR. I just tried such an "internal" test again and tried to use also the JbpmCallback-Service instead of only the action. But I get in both cases only errors like that: 11:52:40,825 INFO [STDOUT] 277838 [WorkManager(2)-4] WARN org.jboss.soa.esb.listeners.message.ActionProcessingPipeline - Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost:2001/queue/CallbackQueue/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost:2001/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] ReplyTo: EPR: PortReference < <wsa:Address logical:JBossESB-Internal#JBpmCallbackService/>, <wsa:ReferenceProperties jbossesb:esbToBpmVars : />, <wsa:ReferenceProperties jbossesb:jbpmTokenId : 2260992/>, <wsa:ReferenceProperties jbossesb:jbpmNodeId : 1998849/>, <wsa:ReferenceProperties jbossesb:jbpmProcessInstId : 2228224/>, <wsa:ReferenceProperties jbossesb:jbpmProcessNodeVersionCounter1998849_2260992 : 0/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/logical/> > MessageID: 12d7505a-7ab0-4392-baf3-4a166f3e0a02 RelatesTo: jms:correlationID#12d7505a-7ab0-4392-baf3-4a166f3e0a02 ] org.jbpm.JbpmException: couldn't execute org.jboss.soa.esb.services.jbpm.cmd.CallbackCommand@4fa1cd at org.jbpm.command.impl.CommandServiceImpl.execute(CommandServiceImpl.java:73) at org.jboss.soa.esb.services.jbpm.cmd.CommandExecutor.executeJbpmCommand(CommandExecutor.java:238) at org.jboss.soa.esb.services.jbpm.cmd.CommandExecutor.access$100(CommandExecutor.java:55) at org.jboss.soa.esb.services.jbpm.cmd.CommandExecutor$3.execute(CommandExecutor.java:145) at org.jboss.soa.esb.services.jbpm.actions.JBpmCallback.process(JBpmCallback.java:68) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Which is currently no problem for me, I'm happy now using the bpmCallback action. I will need a bit more time (hope to have that time the next days) to create again a testing situation where I use direct callbacks and can hopefully also reproduce the time out thing I also described. Then I'll get back to you. Thanks again, Andre View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237837#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...