[
https://issues.apache.org/jira/browse/ARTEMIS-4521?focusedWorklogId=893743&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-893743
]
ASF GitHub Bot logged work on ARTEMIS-4521:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Dec/23 11:41
Start Date: 04/Dec/23 11:41
Worklog Time Spent: 10m
Work Description: AntonRoskvist commented on PR #4697:
URL:
https://github.com/apache/activemq-artemis/pull/4697#issuecomment-1838461087
@erwindon
`the issue here was that deletion using JMX was not updated in the journal,
and the PR seems to fix just that.`
Yes, and I'm saying the same thing happens for diverts configured through
the XML file, but with the addition that the divert is created again directly
after getting removed instead of after a restart.
I do see now though that the setting I mentioned above
`config-delete-diverts = FORCE` might not help in your use-case after all but
for diverts configured through XML it will.
Regardless, I'm not arguing against the change, rather that the
aforementioned config should also be removed as part of it since it will become
non-functional after (as far as I can tell).
Issue Time Tracking
-------------------
Worklog Id: (was: 893743)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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)
