FrameDecoder gets empty buffer

[roboke]

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.