You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2017/02/24 14:54:44 UTC
[jira] [Updated] (ARTEMIS-970)
javax.jms.Message.getJMSDestination() fails when message not sent with AMQP
[ https://issues.apache.org/jira/browse/ARTEMIS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram updated ARTEMIS-970:
-----------------------------------
Summary: javax.jms.Message.getJMSDestination() fails when message not sent with AMQP (was: Artemis Cross Protocol to JMS does not work)
> javax.jms.Message.getJMSDestination() fails when message not sent with AMQP
> ---------------------------------------------------------------------------
>
> Key: ARTEMIS-970
> URL: https://issues.apache.org/jira/browse/ARTEMIS-970
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Martyn Taylor
> Assignee: Justin Bertram
> Fix For: 2.0.0
>
> Attachments: 0001-Test-for-Cross-Protocol.patch
>
>
> After the latest changes around the addressing scheme, the Artemis JMS Core client no longer uses prefixes e.g. "jms.queue." to determine the destination type of a message.
> Instead it relies on a message header sent from the:
> SimpleString HDR_ROUTING_TYPE = new SimpleString("_AMQ_ROUTING_TYPE");
> This currently isn't getting set when doing cross protocol.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)