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

["Justin Bertram (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram updated ARTEMIS-1644:
------------------------------------
    Description: 
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.

> 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)