[jira] [Commented] (ARTEMIS-1644) Legacy clients can't access addresses/queues explicitly configured with "jms.queue." and "jms.topic." prefixes

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on ARTEMIS-1644:
-----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1830

    ARTEMIS-1644 legacy clients can't access resources with old prefixes

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-1644

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1830.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 #1830
    
----
commit 20928c464e23ba93038bd96915767c7ead5bd856
Author: Justin Bertram <jb...@...>
Date:   2018-01-30T19:04:51Z

    ARTEMIS-1644 legacy clients can't access resources with old prefixes

----


> Legacy clients can't access addresses/queues explicitly configured with "jms.queue." and "jms.topic." prefixes
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1644
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1644
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>
> There is logic in the broker to detect legacy clients (i.e. from Artemis 1.5.x and HornetQ) which will:
>  * automatically set anycastPrefix and multicastPrefix to "jms.queue." and "jms.topic." respectively
>  * automatically convert queue/address names in network packets
> In general this works perfectly for legacy clients.  However, if there are addresses or queues on the broker explicitly configured with either "jms.queue." or "jms.topic." then these legacy clients will not be able to access them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)