You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2016/08/23 13:38:20 UTC

[jira] [Commented] (AMQ-6404) AMQP/JMS message transformation broken.

    [ https://issues.apache.org/jira/browse/AMQ-6404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432790#comment-15432790 ] 

Timothy Bish commented on AMQ-6404:
-----------------------------------

Do you have a unit test that can reproduce this.  It's unusual that the content of the message on the broker has been unmarshaled.

> AMQP/JMS message transformation broken.
> ---------------------------------------
>
>                 Key: AMQ-6404
>                 URL: https://issues.apache.org/jira/browse/AMQ-6404
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 5.14.0
>            Reporter: HÃ¥kan Johansson
>            Priority: Critical
>
> The changes introduced by AMQ-6374 broke the transformation between AMQP and JMS for UTF-8 text messages.
> I have enabled the JMS message transformer for the AMQP transport connector. If I send a UTF-8 text message over AMQP and then reads it back over AMQP I get an empty message body.
> I have looked at the code and found the bad code. It is in the {{org.apache.activemq.transport.amqp.message.ActiveMQJMSVendor}} class.
> When the inbound message arrives the {{createTextMessage(String)}} method is called. That method creates an {{ActiveMQTextMessage}} instance whose data is set with the {{setText}} method.
> When the outbound message is to be sent the {{getBinaryFromMessageBody(TextMessage)}} method is called. This method tries to get the data with the {{getContent}} method, but that method always returns {{null}}. The {{getText}} method returns the correct data, but is not used here.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)