[
https://issues.apache.org/jira/browse/ARTEMIS-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144116#comment-17144116
]
ASF subversion and git services commented on ARTEMIS-2819:
----------------------------------------------------------
Commit efb1bd3f9f422e8b6302b6e9a06eb231ef78d79a in activemq-artemis's branch
refs/heads/master from Keith Wall
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=efb1bd3 ]
ARTEMIS-2819 exact match address setting removal ineffective
> Removal of address setting (exact match) ineffective
> ----------------------------------------------------
>
> Key: ARTEMIS-2819
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2819
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.13.0
> Reporter: Keith Wall
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> If, dynamically through management, I add a settings for an address (exact
> match) then later remove those settings, on re-reading the settings record
> for the same address, I expect to see the settings from higher in the
> hierarchy (or the root). This does not occur. It behaves as if the removal
> did not take case.
> I wrote a ActiveMQServerControlTest that demonstrates the problem. Looking at
> the code, it appears the HierarchicalObjectRepository does not remove its
> copy from the cache in the exact match case. Candidate PR raised.
> [https://github.com/apache/activemq-artemis/pull/3199]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
