[
https://issues.apache.org/jira/browse/ARTEMIS-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878658#comment-15878658
]
ASF GitHub Bot commented on ARTEMIS-970:
----------------------------------------
GitHub user jbertram opened a pull request:
https://github.com/apache/activemq-artemis/pull/1037
ARTEMIS-970 handle indeterminate JMS destination
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-970
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1037.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1037
----
commit 6fdcec264a31c5a9660ea025c5c73ecc33fa69a6
Author: Justin Bertram <[email protected]>
Date: 2017-02-22T14:53:09Z
ARTEMIS-970 handle indeterminate JMS destination
----
> Artemis Cross Protocol to JMS does not work
> -------------------------------------------
>
> Key: ARTEMIS-970
> URL: https://issues.apache.org/jira/browse/ARTEMIS-970
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Martyn Taylor
> Assignee: Justin Bertram
> 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)
