[
https://issues.apache.org/jira/browse/ARTEMIS-4521?focusedWorklogId=893677&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-893677
]
ASF GitHub Bot logged work on ARTEMIS-4521:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Dec/23 08:02
Start Date: 04/Dec/23 08:02
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4697:
URL:
https://github.com/apache/activemq-artemis/pull/4697#issuecomment-1838020631
Strange coincidence but I stumbled upon this issue just a few days ago as
well, but from having added and then removed the divert through xml config
(where the divert just remains active instead)... while I highly agree that
this change is good and is how the broker should work, the current behavior is
actually by design... you are supposed to set the address-setting
`config-delete-diverts = FORCE` to enable removal of the diverts.
This is controlled by:
`org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl#recoverStoredDiverts()`
Perhaps this setting should just be removed as well, since with this PR it
will become non-functional?
Issue Time Tracking
-------------------
Worklog Id: (was: 893677)
Time Spent: 20m (was: 10m)
> Deleting divert using management API doesn't remove binding from journal
> ------------------------------------------------------------------------
>
> Key: ARTEMIS-4521
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4521
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.31.2
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After a JMX {{createDivert}} followed by a JMX {{destroyDivert}} followed by
> a broker restart the divert is visible again.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
