FrameDecoder gets empty buffer

["이희승 (Trustin Lee)"]

Netty does not close the connection by itself. It only closes it when 
.close() was called or the peer closed the connection.

What is interesting is that decodeLast() is not called in some cases. 
Could you post the code so that we can reproduce the problem?

Thanks

roboke wrote:
 > Thanks for your answer, Trustin!
 >
 > You're right. The channel is getting closed and therefor the 
decodeLast() is
 > called.
 >
 > What is strange is, that there is no one, that closes the channel. The
 > use-case is, that the handler sends a message downstream and immediatly
 > after the message passed the last encoder the channel is closed. It looks
 > like it's closed by "someone inside netty". But I am sure, there is 
no code
 > of mine performing the close and I am also sure, the receiver of the 
message
 > is not closing the channel.
 > I tried to explicitely close the channel by myself and the behaviour was
 > different. The channel is closed, but the decodeLast is not called. Also
 > when I explicitely closed the channel by the receiver of the message - no
 > decodeLast was called.
 > So my conclusion for now could be, that for some reason netty writes the
 > data to the receiver and then closes the channel without being told to do
 > so.
 >
 > But I assume, that's not how netty works, right?
 >
 > Best regards,
 > roboke
 >
 > --
 > View this message in context: 
http://netty-forums-and-mailing-lists.685743.n2.nabble.com/FrameDecoder-gets-empty-buffer-tp6935816p6940167.html
 > Sent from the Netty User Group mailing list archive at Nabble.com.
 > _______________________________________________
 > netty-users mailing list
 > netty-users at lists.jboss.org
 > https://lists.jboss.org/mailman/listinfo/netty-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/netty-users/attachments/20111028/9cd79387/attachment.html