[jira] [Commented] (CAMEL-6449) Deadlock in camel netty while sending messages to multiple tcp endpoints in single route

["Willem Jiang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683492#comment-13683492 ] 

Willem Jiang commented on CAMEL-6449:
-------------------------------------

Hi kiran,
As you know this issue is fixed last week. Can you check out the last camel 2.12-SNAPSHOT to verify the fix?
                
> Deadlock in camel netty while sending messages to multiple tcp endpoints in single route
> ----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6449
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6449
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-netty
>    Affects Versions: 2.10.4, 2.11.0
>            Reporter: kiran kumar reddy
>             Fix For: 2.10.5, 2.11.1, 2.12.0
>
>         Attachments: MainCamelTest.zip
>
>
> we are getting the following exception when trying to use more than two netty endpoints in a single route. 
> java.lang.IllegalStateException: await*() in I/O thread causes a dead lock or sudden performance drop. Use addListener() instead or call await*() from a different thread. 
> Sample route : 
>                                              from("netty:tcp://localhost:7000textline=true")                               .bean(DummyProcessor.class) 
> .to("netty:tcp://localhost:7001?textline=true")                                 .bean(DummyProcessor.class) 
> .to("netty:tcp://localhost:7002?textline=true") 
> .bean(DummyProcessor.class) 
> .to("netty:tcp://localhost:7003?textline=true") 
> .bean(DummyProcessor.class) 
> .to("netty:tcp://localhost:7004?textline=true") 
> .bean(DummyProcessor.class); 
> camel version : 2.11 
> netty 3.6.5
> The same is working in 2.10.3 version. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira