Re: camel netty deadlock

2013-06-14 Thread kiranreddykasa
Hi Tested the 2.12-SNAPSHOT and it works. So closed this ticket too https://issues.apache.org/jira/browse/CAMEL-6449 - Regards kiran Reddy -- View this message in context: http://camel.465427.n5.nabble.com/camel-netty-deadlock-tp57340

Re: camel netty deadlock

2013-06-14 Thread Claus Ibsen
Hi Fixed by this ticket https://issues.apache.org/jira/browse/CAMEL-6442 On Tue, Jun 11, 2013 at 4:50 PM, kiranreddykasa wrote: > Hi > > I m getting the following exception when trying to use more than two netty > endpoints in a single route. > > java.lang.IllegalStateException: await*() in I/O

Re: camel-netty deadlock when using split in route

2012-04-27 Thread Claus Ibsen
On Fri, Apr 27, 2012 at 10:06 PM, andlu702 wrote: > Tried 2.10-SNAPSHOT and it works like a charm. > > But as I thought I had to update all other camel dependencies to > 2.10-SNAPSHOT as well. > Yeah would would need to upgrade. But I think 2.9 SNAPSHOT may also be fixed. > -- > View this messag

Re: camel-netty deadlock when using split in route

2012-04-27 Thread andlu702
Tried 2.10-SNAPSHOT and it works like a charm. But as I thought I had to update all other camel dependencies to 2.10-SNAPSHOT as well. -- View this message in context: http://camel.465427.n5.nabble.com/camel-netty-deadlock-when-using-split-in-route-tp5670114p5671366.html Sent from the Camel - Us

Re: camel-netty deadlock when using split in route

2012-04-27 Thread andlu702
Thanks for the reseponse. Is it possible to use a different version of camel-netty than that of camel-core? If it forces me to upgrade the camel-core version then it's probably not a realistic solution in this project. Since I have control over the producer I made a workaround for now and that i

Re: camel-netty deadlock when using split in route

2012-04-27 Thread Claus Ibsen
Hi Can you try with 2.10 SNAPSHOT as camel-netty have been improved in that release. On Fri, Apr 27, 2012 at 2:17 PM, andlu702 wrote: > I found dead post on this forum which seem quite similar to the problem I'm > experiencing, but I decided to create a new thread instead of waking up a > zombi