camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9368) Netty4 producer hangs when connection is prematurely closed
Date Tue, 01 Dec 2015 13:40:11 GMT

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

Claus Ibsen commented on CAMEL-9368:
------------------------------------

Yeah it may be that on the producer side if you have explicit disconnect=true or keepAlive=false,
then the propagation of channelInactive is maybe not needed. If you still do that, then netty
causes this to propgate as channelException or what its called, and then the producer thinks
there was an exception and causes the exchange to fail. But it should not fail, as the producer
received the response from the remote server, but the channel was just closed as expected
also.

> Netty4 producer hangs when connection is prematurely closed
> -----------------------------------------------------------
>
>                 Key: CAMEL-9368
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9368
>             Project: Camel
>          Issue Type: Bug
>            Reporter: Jonathan Anstey
>            Assignee: Jonathan Anstey
>             Fix For: 2.16.2, 2.15.5, 2.17.0
>
>
> Netty4 producer is reusing connections and implementing a request-response style protocol.
If the server closes socket connection after reading request packet and prior to sending back
response packet, Netty4 producer hangs. If, on the other hand, the server closes socket after
sending back response and does not bother to read next request, then producer does not hang.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message