[
https://issues.apache.org/activemq/browse/AMQNET-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39386
]
Jonas Larsson commented on AMQNET-46:
-------------------------------------
This bug should be quite easy to fix by applying the patch.
We are currently running this patched version in production.
> ActiveMQTextMessage is not encoding strings properly as UTF-8
> -------------------------------------------------------------
>
> Key: AMQNET-46
> URL: https://issues.apache.org/activemq/browse/AMQNET-46
> Project: ActiveMQ .Net
> Issue Type: Bug
> Reporter: Jonas Larsson
> Assignee: James Strachan
> Priority: Critical
> Attachments: utf8fix.patch
>
>
> Non ASCII characters in the Payload of a TextMessage is not properly encoded
> to UTF-8 when sent over the wire.
> This causes the ActiveMQ server to throw an exception like this and is
> blocking for supporting nationalized characters (such as Chinese):
> javax.jms.JMSException: java.io.UTFDataFormatException
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:58)
> at
> org.apache.activemq.command.ActiveMQTextMessage.getText(ActiveMQTextMessage.java:87)
> at
> com.mansion.integration.playtech.AccountEventListener.onMessage(AccountEventListener.java:174)
> Attached is a patch that fixes the problem for the message body, but the
> problem probably exists for String properties also.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
