activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Pitkin (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-919) Issues creating jms queues in core config in broker.xml
Date Wed, 25 Jan 2017 13:37:27 GMT


Andy Pitkin commented on ARTEMIS-919:

I have also run into this issue using 1.5.1 where queues defined under the core element are
getting prefixed with jms.queue (no matter what the queue name is). The issue is fairly major
as this only happens when the configuration file is reloaded during runtime, meaning the exact
same broker.xml will create a new set of queues on restart without the jms.queue prefix.

> Issues creating jms queues in core config in broker.xml
> -------------------------------------------------------
>                 Key: ARTEMIS-919
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.5.1
>            Reporter: Thorsten Kunz
>            Assignee: Justin Bertram
> I have the following broker configuration snippet:
> {quote}
>    <core xmlns="urn:activemq:core">
>       <queues>
>         <queue name="jms.queue.SOME.FEED.CONSUMER_A">
>           <address>jms.queue.SOME.FEED</address>
>           <durable>true</durable>
>         </queue>
>         <queue name="jms.queue.SOME.FEED.CONSUMER_B">
>           <address>jms.queue.SOME.FEED</address>
>           <durable>true</durable>
>         </queue>
>       </queues>
> {quote}
> The goal is to send to one JMS queue but consume the massages from two different queues.
> But then I load this config Artemis creates two queues:
>  - jms.queue.jms.queue.SOME.FEED.CONSUMER_A
>  - jms.queue.jms.queue.SOME.FEED.CONSUMER_B
> So for some reason it is duplicating the "jms.queue" prefix. But when I don't put the
"jms.queue" as prefix is doesn't add it at all. So I have no way to create a JMS queue with
different name and address in the core config.

This message was sent by Atlassian JIRA

View raw message