FrameDecoder gets empty buffer
"이희승 (Trustin Lee)"
trustin at gmail.com
Thu Oct 27 14:28:01 EDT 2011
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.
HTH
roboke wrote:
> Hi folks!
>
> I am currently experiencing an implementation of mine, that is
extending the
> FrameDecoder, is triggered with an empty buffer. I really don't know how
> this is possible, but I am quite sure I got it right. The "decode()"
method
> is called with an empty buffer. readableBytes() is 0 and the backing
array
> seems to be 256 times 0.
>
> Does any one know how to handle this? It's my first netty-project, so
I may
> have some configuration issues, but I also double-checked the
alignment of
> the components on my pipeline.
>
> Best regards,
> Roboke
>
> --
> View this message in context:
http://netty-forums-and-mailing-lists.685743.n2.nabble.com/FrameDecoder-gets-empty-buffer-tp6935816p6935816.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/20111027/d4978f32/attachment.html
More information about the netty-users
mailing list