Hi

Can you try adding

<convertBodyTo type="String"/> at the end of the route, to ensure the
message is loaded into memory and not stream based, so the CXF
consumer uses that as reply.



On Mon, Oct 14, 2013 at 4:25 PM, javakurious <javakuri...@gmail.com> wrote:
> Thanks for your patience and help..
>
> Yes, the response from Netty (when synchronous = false) is always logged  in
> #6 with or without Netty. But the response is not always received back by
> cxf consumer. The webservice client sees the response, say, 1 out of 10
> times.
>
> However, if I comment out Netty, everything flows perfectly, in terms of
> every component seeing the body.
>
> I enabled streamCaching by setting streamCache="true" in the route, but that
> did not help much. Though, it does seem that the WebService client might be
> seeing the response a little more frequently. Before, it probably was
> something like 1 out of 15 times. But that could be just me imagining
> things..
>
> Thanks.
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Netty-messages-not-propagated-back-from-netty-producer-tp5741315p5741537.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Reply via email to