You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Manu Lopez <ml...@intecna.es> on 2007/03/26 12:49:16 UTC
Invalid response state for mex....
Hi
I've just install the last revision of Apache Ode using the JBI component in
Servicemix.
Before this, I was able to run all my bpel processes packaged in a Service
Assembly in Servicemix, but with this new version of Ode, the soap message
response is never returned.
I invoke the bpel process with the sendsoap.sh command. The proccess seems
to work fine until the reply operation. At this point, I get the next error
in console:
ERROR - BpelRuntimeContextImpl - Invalid response state for mex
hqejbhcnphr255b0tpghnk: ASYNC
In servicemix.log, I can see the soap response, which is successfully
generated, but is no returned:
<?xml version="1.0" encoding="UTF-8"?>
<getTicketResponse xmlns="http://webservices.xxxx.es/">
<out>eintegra-2-xRHzFD7f4ErZ4czB1NYA7ehvcgNBQJmsqaQ</out>
</getTicketResponse>
If I change to a older version of ODE, It works ok.
--
View this message in context: http://www.nabble.com/Invalid-response-state-for-mex....-tf3466275.html#a9671004
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Invalid response state for mex....
Posted by Alex Boisvert <bo...@intalio.com>.
Hi Manu,
Could you put together a service assembly that reproduces this? It would
help me diagnose the issue.
thanks,
alex
On 3/26/07, Manu Lopez <ml...@intecna.es> wrote:
>
>
> Hi
>
> I've just install the last revision of Apache Ode using the JBI component
> in
> Servicemix.
>
> Before this, I was able to run all my bpel processes packaged in a Service
> Assembly in Servicemix, but with this new version of Ode, the soap message
> response is never returned.
> I invoke the bpel process with the sendsoap.sh command. The proccess seems
> to work fine until the reply operation. At this point, I get the next
> error
> in console:
>
> ERROR - BpelRuntimeContextImpl - Invalid response state for mex
> hqejbhcnphr255b0tpghnk: ASYNC
>
> In servicemix.log, I can see the soap response, which is successfully
> generated, but is no returned:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <getTicketResponse xmlns="http://webservices.xxxx.es/">
> <out>eintegra-2-xRHzFD7f4ErZ4czB1NYA7ehvcgNBQJmsqaQ</out>
> </getTicketResponse>
>
> If I change to a older version of ODE, It works ok.
>
> --
> View this message in context:
> http://www.nabble.com/Invalid-response-state-for-mex....-tf3466275.html#a9671004
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>
Re: Invalid response state for mex....
Posted by Alex Boisvert <bo...@intalio.com>.
Hi Manu,
I've committed a fix for this in the trunk. Can you update and try again?
thanks,
alex
On 3/26/07, Manu Lopez <ml...@intecna.es> wrote:
>
>
> Hi
>
> I've just install the last revision of Apache Ode using the JBI component
> in
> Servicemix.
>
> Before this, I was able to run all my bpel processes packaged in a Service
> Assembly in Servicemix, but with this new version of Ode, the soap message
> response is never returned.
> I invoke the bpel process with the sendsoap.sh command. The proccess seems
> to work fine until the reply operation. At this point, I get the next
> error
> in console:
>
> ERROR - BpelRuntimeContextImpl - Invalid response state for mex
> hqejbhcnphr255b0tpghnk: ASYNC
>
> In servicemix.log, I can see the soap response, which is successfully
> generated, but is no returned:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <getTicketResponse xmlns="http://webservices.xxxx.es/">
> <out>eintegra-2-xRHzFD7f4ErZ4czB1NYA7ehvcgNBQJmsqaQ</out>
> </getTicketResponse>
>
> If I change to a older version of ODE, It works ok.
>
> --
> View this message in context:
> http://www.nabble.com/Invalid-response-state-for-mex....-tf3466275.html#a9671004
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>