You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2005/02/06 06:41:26 UTC

[jira] Closed: (DIRMINA-4) ProtocolDecoder receives dirty ByteBuffer in UDP mode.

     [ http://issues.apache.org/jira/browse/DIRMINA-4?page=history ]
     
Trustin Lee closed DIRMINA-4:
-----------------------------

    Resolution: Fixed

Fixed at: http://svn.apache.org/viewcvs?view=rev&rev=151546

IoAdapter did not discard unread part of previous ByteBuffer and called decoder.decode() with it again.  Now IoAdapter discards ByteBuffer even if the decoder didn't read all part of ByteBuffer.  If decoder couldn't decode some end part of ByteBuffer because the message was not complete, decoder will have to buffer it to merge it with the next ByteBuffer.

DhcpMessageEncoder triggered this bug because it didn't read all packet.

> ProtocolDecoder receives dirty ByteBuffer in UDP mode.
> ------------------------------------------------------
>
>          Key: DIRMINA-4
>          URL: http://issues.apache.org/jira/browse/DIRMINA-4
>      Project: MINA
>         Type: Bug
>     Versions: 0.7
>     Reporter: Trustin Lee
>     Assignee: Trustin Lee
>      Fix For: 0.7

>
> ProtocolDecoder received dirty ByteBuffers in UDP mode.  This never happened in TCP mode.  It can be reproduced using DHCP server Enrique wrote.  Enrique told me that it is OK if decoder rewinds the dirty buffer which means just the position of the buffer changed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira