<HTML><HEAD><META content="text/html; charset=UTF-8" http-equiv="Content-Type"></HEAD><BODY>Netty does not close the connection by itself. It only closes it when .close() was called or the peer closed the connection.<BR>
<BR>
What is interesting is that decodeLast() is not called in some cases. Could you post the code so that we can reproduce the problem?<BR>
<BR>
Thanks<BR>
<BR>
roboke wrote:<BR>
> Thanks for your answer, Trustin!<BR>
><BR>
> You're right. The channel is getting closed and therefor the decodeLast() is<BR>
> called.<BR>
><BR>
> What is strange is, that there is no one, that closes the channel. The<BR>
> use-case is, that the handler sends a message downstream and immediatly<BR>
> after the message passed the last encoder the channel is closed. It looks<BR>
> like it's closed by "someone inside netty". But I am sure, there is no code<BR>
> of mine performing the close and I am also sure, the receiver of the message<BR>
> is not closing the channel.<BR>
> I tried to explicitely close the channel by myself and the behaviour was<BR>
> different. The channel is closed, but the decodeLast is not called. Also<BR>
> when I explicitely closed the channel by the receiver of the message - no<BR>
> decodeLast was called.<BR>
> So my conclusion for now could be, that for some reason netty writes the<BR>
> data to the receiver and then closes the channel without being told to do<BR>
> so.<BR>
><BR>
> But I assume, that's not how netty works, right?<BR>
><BR>
> Best regards,<BR>
> roboke<BR>
><BR>
> --<BR>
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/FrameDecoder-gets-empty-buffer-tp6935816p6940167.html<BR>
> Sent from the Netty User Group mailing list archive at Nabble.com.<BR>
> _______________________________________________<BR>
> netty-users mailing list<BR>
> netty-users@lists.jboss.org<BR>
> https://lists.jboss.org/mailman/listinfo/netty-users</BODY></HTML>