Request-Reply a second route

[Gabriel <ga...@unitybox.de>]

Hello,
I have a route which proxies another route with a web-service like this (1.
Route:): 


from("cxf:bean:TpmsWSEndpoint")
               
.inOut("activemq:queue:tpms_sendTo_iccs?replyTo=tpms_from_iccs&jmsMessageType=Text");

The activemq:queue:tpms_sendTo_iccs queue is the beginning of an other route
witch also have a request-reply request like so (2. Route:)

from("activemq:queue:tpms_sendTo_iccs?useMessageIDAsCorrelationID=true").
inOut("activemq:queue:iccs.request?jmsMessageType=Text").
 to("activemq:queue:tpms_from_iccs");          

I'm loosing all header at the inout call. The Message is processed
succsessfully and resists in activemq:queue:tpms_from_iccs. The 1. Route
gets an timeout exception.

How can I fix that, any ideas?




--
View this message in context: http://camel.465427.n5.nabble.com/Request-Reply-a-second-route-tp5742211.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Request-Reply a second route

[Christian Posta <ch...@gmail.com>]

Any particular reason why you're using "message ID as correlationID == true?"
Also, the exchange pattern would be InOut, so you don't need to
explicitly send the message to tpms_from_iccs

I have written a unit test that passes; you should take a look at it here:

https://github.com/christian-posta/camel-sandbox/blob/master/camel-2.12.1-issues/src/test/java/posta/NestedJmsReqReplyTest.java

On Fri, Oct 25, 2013 at 7:06 AM, Gabriel <ga...@unitybox.de> wrote:
> Hello,
> I have a route which proxies another route with a web-service like this (1.
> Route:):
>
>
> from("cxf:bean:TpmsWSEndpoint")
>
> .inOut("activemq:queue:tpms_sendTo_iccs?replyTo=tpms_from_iccs&jmsMessageType=Text");
>
> The activemq:queue:tpms_sendTo_iccs queue is the beginning of an other route
> witch also have a request-reply request like so (2. Route:)
>
> from("activemq:queue:tpms_sendTo_iccs?useMessageIDAsCorrelationID=true").
> inOut("activemq:queue:iccs.request?jmsMessageType=Text").
>  to("activemq:queue:tpms_from_iccs");
>
> I'm loosing all header at the inout call. The Message is processed
> succsessfully and resists in activemq:queue:tpms_from_iccs. The 1. Route
> gets an timeout exception.
>
> How can I fix that, any ideas?
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Request-Reply-a-second-route-tp5742211.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta

Re: Request-Reply a second route

[Willem jiang <wi...@gmail.com>]

I think it is depends how your route consume the message from the iccs.request queue.


--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
          http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem





On Friday, October 25, 2013 at 10:06 PM, Gabriel wrote:

> Hello,
> I have a route which proxies another route with a web-service like this (1.
> Route:):  
>  
>  
> from("cxf:bean:TpmsWSEndpoint")
>  
> .inOut("activemq:queue:tpms_sendTo_iccs?replyTo=tpms_from_iccs&jmsMessageType=Text");
>  
> The activemq:queue:tpms_sendTo_iccs queue is the beginning of an other route
> witch also have a request-reply request like so (2. Route:)
>  
> from("activemq:queue:tpms_sendTo_iccs?useMessageIDAsCorrelationID=true").
> inOut("activemq:queue:iccs.request?jmsMessageType=Text").
> to("activemq:queue:tpms_from_iccs");  
>  
> I'm loosing all header at the inout call. The Message is processed
> succsessfully and resists in activemq:queue:tpms_from_iccs. The 1. Route
> gets an timeout exception.
>  
> How can I fix that, any ideas?
>  
>  
>  
>  
> --
> View this message in context: http://camel.465427.n5.nabble.com/Request-Reply-a-second-route-tp5742211.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).