You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2011/01/24 16:41:46 UTC

[jira] Resolved: (AMQCPP-346) No UTF8 conversation in OpenWire strings

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

Timothy Bish resolved AMQCPP-346.
---------------------------------

    Resolution: Fixed

Fixed in trunk.

> No UTF8 conversation in OpenWire strings
> ----------------------------------------
>
>                 Key: AMQCPP-346
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-346
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 3.1.3, 3.2.0, 3.2.1, 3.2.2, 3.2.3, 3.2.4
>         Environment: Windows XP/VISTA/7
>            Reporter: Peter Pfort
>            Assignee: Timothy Bish
>
> Hello,
> I have found a bug in the implementation of the OpenWire protocol. When you have non ascii character i.e. in the selector of a topic consumer, then the program hangs in createConsumer.
> The problem is in the class BaseDataStreamMarshaller. In BaseDataStreamMarshaller::tightMarshalString1() thinks, the string will be converted to UTF8, but BaseDataStreamMarshaller::tightMarshalString2() write out the string with dataOut->writeChars( value );
> I have changed BaseDataStreamMarshaller::tightMarshalString2() to dataOut->writeUTF( value ); and everything works fine.
> Please correct it in the source.
> Best regards

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