You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2007/02/20 08:46:05 UTC

[jira] Resolved: (DIRMINA-296) ByteBuffer.limit() incorrect when CharacterCodingException() occurred

     [ https://issues.apache.org/jira/browse/DIRMINA-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Trustin Lee resolved DIRMINA-296.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.2
         Assignee: Trustin Lee

Thank you for the test case and pin-pointing screenshot.  The fix has been applied to all branches.

> ByteBuffer.limit() incorrect when CharacterCodingException() occurred
> ---------------------------------------------------------------------
>
>                 Key: DIRMINA-296
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-296
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0
>         Environment: Window/Unix
>            Reporter: Phan Thanh Hieu
>         Assigned To: Trustin Lee
>             Fix For: 1.0.2
>
>         Attachments: ByteBuffer.java, bytebuffer.jpg, TestByteBuffer.java
>
>
> ByteBuffer.limit() is INCORRECT when CharacterCodingException occurred.
> Information: my app just support ASCII-character messages. So when receiving non-ASCII message => CharacterCodingException occurrec and my expected action: save the raw-data into a Error file but the limit of the ByteBuffer is changed so i could not save whole raw data to this kind of file.
> I have reviewed the getString() method of MINA ByteBuffer. I could found the problem, please see the attachment.
> Thanks, Hieu Phan.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.