[ARTEMIS-919] Issues creating jms queues in core config in broker.xml when hot reloading configuration

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.1, 1.5.3
• Fix Version/s: 1.5.4, 2.0.0
• Assignee: Justin Bertram
• Reporter: Thorsten Kunz
• Created: 13/Jan/17 12:09
• Updated: 31/Aug/17 19:12
• Resolved: 28/Feb/17 20:13

Description

I have the following broker configuration snippet:

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

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.

Issue Links

• links to: GitHub Pull Request #1056
• links to: GitHub Pull Request #1057