You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Krzysztof Jamróz (Jira)" <ji...@apache.org> on 2021/02/17 10:56:00 UTC

[jira] [Updated] (CAMEL-16227) Netty with reuseChannel=true invokes wrong callback

     [ https://issues.apache.org/jira/browse/CAMEL-16227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krzysztof Jamróz updated CAMEL-16227:
-------------------------------------
    Attachment: NettyReuseChannelCallbackTest.java

> Netty with reuseChannel=true invokes wrong callback
> ---------------------------------------------------
>
>                 Key: CAMEL-16227
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16227
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-netty
>    Affects Versions: 3.7.2
>            Reporter: Krzysztof Jamróz
>            Priority: Major
>         Attachments: NettyReuseChannelCallbackTest.java
>
>
> Netty when configured with {{reuseChannel=true}} invokes wrong {{AsyncCallback}}. It invokes callback registered by first netty invocation in given route multiple times. This can be observed by debugging {{NettyReuseChannelTest}}. This seems not to cause serious problems at least in simple cases, because both callbacks (from {{SendProcessor}}) do not do much and simply continue routing. I am not sure if in more complex cases this could cause more problems.
> However there is one observable issue caused by this behavior: event notifications contain wrong endpoint and wrong time taken. I attached a test for it.
> Another problem is that this behavior makes it harder (if possible at all) to fix CAMEL-16178 for case with {{reuseChannel=true}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)