> And the related internal address cannot be deleted due to the presence of the divert to it.
Can you confirm that you can't delete an address when it has no queues and it is the "forwarding-address" target of a divert? I just tested this and I was able to delete such an address. Justin On Fri, Oct 27, 2023 at 10:43 AM Dondorp, Erwin <erwin.dond...@ns.nl.invalid> wrote: > Non-Business > > Hello, > > For any "retro-active" address in Artemis (see > https://activemq.apache.org/components/artemis/documentation/latest/retroactive-addresses.html) > a few objects are created beyond what happens for a regular address: > > 1. A divert on the original address; and > 2. A related internal address ($.something); and > 3. A queue on the related internal address for anycast; and > 4. A queue on the related internal address for multicast. > > We use auto-create for all our objects. But it is hard to get rid of these > objects once they are no longer needed. The original address cannot be not > deleted due to the presence of the divert. And the related internal address > cannot be deleted due to the presence of the divert to it. The 2 internal > queues can be deleted manually though. > > Does anyone have tips or tricks to completely clean-up obsolete > retro-active addresses, without server downtime? > > thx! > Erwin > > ________________________________ > > Deze e-mail, inclusief eventuele bijlagen, is uitsluitend bestemd voor > (gebruik door) de geadresseerde. De e-mail kan persoonlijke of > vertrouwelijke informatie bevatten. Openbaarmaking, vermenigvuldiging, > verspreiding en/of verstrekking van (de inhoud van) deze e-mail (en > eventuele bijlagen) aan derden is uitdrukkelijk niet toegestaan. Indien u > niet de bedoelde geadresseerde bent, wordt u vriendelijk verzocht degene > die de e-mail verzond hiervan direct op de hoogte te brengen en de e-mail > (en eventuele bijlagen) te vernietigen. > > Informatie vennootschap<http://www.ns.nl/emaildisclaimer> >
