Without encoders and decoders of netty it is working as expected.
Any alternate for the encoders and decoders??
-
Regards
kiran Reddy
--
View this message in context:
http://camel.465427.n5.nabble.com/netty-open-close-tp5733304p5733372.html
Sent from the Camel - Users mailing list archive
Hi as per our observation we are getting ClosedChannelException when the
remote machine is restarted.
It's not trying to reconnect.
-
Regards
kiran Reddy
--
View this message in context:
http://camel.465427.n5.nabble.com/netty-open-close-tp5733304p5733364.html
Sent from the Camel - Users
As of now we are using these parameters , Still its not working.
sync=true&lazyChannelCreation=false&producerPoolEnabled=false&disconnect=true
-
Regards
kiran Reddy
--
View this message in context:
http://camel.465427.n5.nabble.com/netty-open-close-tp5733304p5733326.html
Sent from the Cam
You can try turning producer pooling off,
producerPoolEnabled=false
On Tue, May 28, 2013 at 9:40 AM, kiranreddykasa wrote:
> camel : 2.10.4
>
> netty : netty-3.5.11.Final
>
>
>
> -
> Regards
>
> kiran Reddy
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/netty-open
camel : 2.10.4
netty : netty-3.5.11.Final
-
Regards
kiran Reddy
--
View this message in context:
http://camel.465427.n5.nabble.com/netty-open-close-tp5733304p5733320.html
Sent from the Camel - Users mailing list archive at Nabble.com.
What version of Camel and Netty do you use?
On Tue, May 28, 2013 at 9:10 AM, kiranreddykasa wrote:
> Tried that too.But still no luck.
>
>
> I guess its not even trying to open the connection again.
>
>
>
> -
> Regards
>
> kiran Reddy
> --
> View this message in context:
> http://camel.46542
Tried that too.But still no luck.
I guess its not even trying to open the connection again.
-
Regards
kiran Reddy
--
View this message in context:
http://camel.465427.n5.nabble.com/netty-open-close-tp5733304p5733313.html
Sent from the Camel - Users mailing list archive at Nabble.com.
You can just use Camels error handler to retry
On Tue, May 28, 2013 at 8:30 AM, kiranreddykasa wrote:
> Ya i tried that.
>
> But the problem is here all the tcp stations are same (Same Ip and port).
>
> So after disconnecting it's not trying to connect again.
>
>
>
>
> -
> Regards
>
> kiran
Ya i tried that.
But the problem is here all the tcp stations are same (Same Ip and port).
So after disconnecting it's not trying to connect again.
-
Regards
kiran Reddy
--
View this message in context:
http://camel.465427.n5.nabble.com/netty-open-close-tp5733304p5733308.html
Sent from
Hi
Try with disconnect=true as documented at
http://camel.apache.org/netty
On Tue, May 28, 2013 at 8:03 AM, kiranreddykasa wrote:
> Hi
>
> According to our use case we have built a route like this.
>
> from(jms).to(tcp netty).to(processor).to(tcp netty ) .to(processor).to(tcp
> netty )
>
> Here
10 matches
Mail list logo