You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Erwin Dondorp (Jira)" <ji...@apache.org> on 2021/06/11 23:41:00 UTC

[jira] [Updated] (ARTEMIS-3343) duplicate address-setting gets lost

     [ https://issues.apache.org/jira/browse/ARTEMIS-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erwin Dondorp updated ARTEMIS-3343:
-----------------------------------
    Description: 
In setting file `broker.xml`, it is possible to register multiple `address-setting` blocks for the same `match`. But because these blocks are put in a `Map` (in `org.apache.activemq.artemis.core.deployers.impl.parseAddressSettings()`), any previous block with the same `match` will be effectively ignored.

This may also happen for some of the other named blocks.

My suggestion is to raise an error when configuration information is lost.

  was:
In setting file `broker.xml`, it is possible to register multiple `address-setting` blocks for the same `match`. But because these blocks are put in a `Map` (in `org.apache.activemq.artemis.core.deployers.impl.parseAddressSettings()`), any previous block with the same `match` will be effectively ignored.

This may also happen for some of the other named blocks.


> duplicate address-setting gets lost
> -----------------------------------
>
>                 Key: ARTEMIS-3343
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3343
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: 2.17.0
>            Reporter: Erwin Dondorp
>            Priority: Major
>
> In setting file `broker.xml`, it is possible to register multiple `address-setting` blocks for the same `match`. But because these blocks are put in a `Map` (in `org.apache.activemq.artemis.core.deployers.impl.parseAddressSettings()`), any previous block with the same `match` will be effectively ignored.
> This may also happen for some of the other named blocks.
> My suggestion is to raise an error when configuration information is lost.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)