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

["Thorsten Kunz (JIRA)" <ji...@apache.org>]

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

Thorsten Kunz commented on ARTEMIS-919:
---------------------------------------

[~jbertram] now that we know how to reproduce the issue could you maybe have another look at it? It is really a blocker to migrate anything to Artemis because a broker.xml reload is renaming all JMS queues configured in core. Sadly core is the only place where some advanced queue configuration can be done. Thanks

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