activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1644) Legacy clients can't access addresses/queues explicitly configured with "jms.queue." and "jms.topic." prefixes
Date Wed, 31 Jan 2018 15:10:00 GMT


ASF GitHub Bot commented on ARTEMIS-1644:

Github user clebertsuconic commented on a diff in the pull request:
    --- Diff: artemis-cli/src/main/resources/org/apache/activemq/artemis/cli/commands/etc/broker.xml
    @@ -78,7 +78,7 @@ ${global-max-section}
              <!-- amqpLowCredits: The server will send the # credits specified at amqpCredits
at this low mark -->
              <!-- Acceptor for every supported protocol -->
    -         <acceptor name="artemis">tcp://${host}:${default.port}?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300</acceptor>
    +         <acceptor name="artemis">tcp://${host}:${default.port}?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.;tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300</acceptor>
    --- End diff --
    @jbertram  but isn't this changing the behaviour for old clients? say if you don't change
the config.

> Legacy clients can't access addresses/queues explicitly configured with "jms.queue."
and "jms.topic." prefixes
> --------------------------------------------------------------------------------------------------------------
>                 Key: ARTEMIS-1644
>                 URL:
>             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."
>  * 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

View raw message