<HTML><HEAD><META content="text/html; charset=UTF-8" http-equiv="Content-Type"></HEAD><BODY>Perhaps it's being triggered by the default implementation of decodeLast(). On disconnection, decodeLast() will be called to give a decoder a chance to clean up its stuff. Could you override decodeLast() to confirm this is the case? Anyway, you can simply ignore the empty buffer.<BR>
<BR>
HTH<BR>
<BR>
roboke wrote:<BR>
> Hi folks!<BR>
><BR>
> I am currently experiencing an implementation of mine, that is extending the<BR>
> FrameDecoder, is triggered with an empty buffer. I really don't know how<BR>
> this is possible, but I am quite sure I got it right. The "decode()" method<BR>
> is called with an empty buffer. readableBytes() is 0 and the backing array<BR>
> seems to be 256 times 0.<BR>
><BR>
> Does any one know how to handle this? It's my first netty-project, so I may<BR>
> have some configuration issues, but I also double-checked the alignment of<BR>
> the components on my pipeline.<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-tp6935816p6935816.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>