be a defect in the
netty producer.
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: Sunday, August 22, 2010 9:02 AM
To: users@camel.apache.org
Subject: Re: netty issue
On Thu, Aug 19, 2010 at 11:20 PM, Sadanand Kusma wrote:
> As suggested, I tried this wi
ricFileMessage with body: Bye 1hello1]
>
The TCP server did not reply within the 30 seconds default timeout. So
check the TCP server what is happening.
>
> -Original Message-
> From: Claus Ibsen [mailto:claus.ib...@gmail.com]
> Sent: Thursday, August 19, 2010 11:06 AM
> To: u
gmail.com]
Sent: Thursday, August 19, 2010 11:06 AM
To: users@camel.apache.org
Subject: Re: netty issue
On Thu, Aug 19, 2010 at 4:45 PM, Sadanand Kusma wrote:
> Thanks for the response, if you set sync=true doesn't it make a synchronous
> call.
> Are you saying that it always runs
e reply to come back from the TCP server.
We should maybe @deprecate sync option and let it check the MEP of the Exchange.
> -Original Message-
> From: Willem Jiang [mailto:willem.ji...@gmail.com]
> Sent: Wednesday, August 18, 2010 10:43 PM
> To: users@camel.apache.org
>
would
have a tracking number to relate request and corresponding response.
-Original Message-
From: Claus Ibsen [mailto:claus.ib...@gmail.com]
Sent: Thursday, August 19, 2010 10:48 AM
To: users@camel.apache.org
Subject: Re: netty issue
What version of Camel are you using?
And why do
do we tell it to run
> in an async mode?.
>
> -Original Message-
> From: Willem Jiang [mailto:willem.ji...@gmail.com]
> Sent: Wednesday, August 18, 2010 10:43 PM
> To: users@camel.apache.org
> Subject: Re: netty issue
>
> I just checked the netty's doc and
10 10:43 PM
To: users@camel.apache.org
Subject: Re: netty issue
I just checked the netty's doc and camel-netty producer's code, if you
set the sync=false, the producer will never expect the response, and the
async callback will never be called.
So you just need to change your route li
I just checked the netty's doc and camel-netty producer's code, if you
set the sync=false, the producer will never expect the response, and the
async callback will never be called.
So you just need to change your route like this
from("file:///test/test/response")
.convertBodyTo(
