activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-919) Issues creating jms queues in core config in broker.xml when hot reloading configuration
Date Tue, 28 Feb 2017 20:09:45 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888786#comment-15888786
] 

Justin Bertram commented on ARTEMIS-919:
----------------------------------------

I sent a pull-request with a fix for this issue.  However, it's worth noting that it might
not behave as you expect.  On the 1.x branch reloading was only ever supported for *JMS* destinations.
 The bug you saw was caused by the reloader grabbing every XML element name {{queue}} (which
mistakenly include core queues) rather than just {{queue}} elements from {{jms}}.

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

Mime
View raw message