You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2017/02/28 20:13:45 UTC
[jira] [Resolved] (ARTEMIS-919) Issues creating jms queues in core
config in broker.xml when hot reloading configuration
[ https://issues.apache.org/jira/browse/ARTEMIS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-919.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.5.4
2.0.0
Although the {{jms}} element is no longer valid on the master branch the code to reload JMS destinations still exists so I fixed it there too.
> Issues creating jms queues in core config in broker.xml when hot reloading configuration
> ----------------------------------------------------------------------------------------
>
> Key: ARTEMIS-919
> URL: https://issues.apache.org/jira/browse/ARTEMIS-919
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 1.5.1, 1.5.3
> Reporter: Thorsten Kunz
> Assignee: Justin Bertram
> Fix For: 2.0.0, 1.5.4
>
>
> 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
(v6.3.15#6346)