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).
