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

Timothy A. Bish resolved QPIDJMS-572.
-------------------------------------
    Resolution: Fixed

> The internal Netty ReadableBuffer wrapper read string API not advancing 
> position index
> --------------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-572
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-572
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 2.0.0
>            Reporter: Timothy A. Bish
>            Assignee: Timothy A. Bish
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> The ReadableBuffer API from proton-j provides methods for reading a string 
> from the remaining readable bytes in the buffer and documents these methods 
> should advance the read index to the limit on return.  The Qpid JMS readable 
> buffer isn't advancing the position as it passes the decoding off to a Netty 
> toString call which does not advance the read index.  This is masked in 
> proton-j currently as all string decodes are done from slices of a buffer or 
> in some cases a duplicate and the buffer slice is cast off afterwards without 
> care for any remaining bytes. Should proton-j be updated to not rely on 
> slices for every single string decode this breaks the codec.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to