activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AMQ-6404) AMQP/JMS message transformation broken.
Date Tue, 23 Aug 2016 14:08:20 GMT


ASF subversion and git services commented on AMQ-6404:

Commit 680d082a179902d14cf38a8afde7c2c12a062106 in activemq's branch refs/heads/activemq-5.14.x
from [~tabish121]
[;h=680d082 ]

Add check for unmarshalled text body and handle that case.
(cherry picked from commit 1030fb184216d00e3fd43a416931acd3b2fc6794)

> AMQP/JMS message transformation broken.
> ---------------------------------------
>                 Key: AMQ-6404
>                 URL:
>             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}}
> When the inbound message arrives the {{createTextMessage(String)}} method is called.
That method creates an {{ActiveMQTextMessage}} instance whose data is set with the {{setText}}
> 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

View raw message