-
Bug
-
Resolution: Unresolved
-
Major
-
AMQ 7.7.0.CR1
-
None
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 upstream.