You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/07/06 19:06:00 UTC
[jira] [Commented] (ARTEMIS-3343) duplicate address-setting gets
lost
[ https://issues.apache.org/jira/browse/ARTEMIS-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17375952#comment-17375952 ]
ASF subversion and git services commented on ARTEMIS-3343:
----------------------------------------------------------
Commit 47d4b8fff441b936cee2a63be27944b93b27e858 in activemq-artemis's branch refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=47d4b8f ]
ARTEMIS-3343 log WARN & ignore duplicate address-setting match
> 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
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> 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)