Hi Justin.
Thanks a lot!

пн, 12 янв. 2026 г. в 22:58, Justin Bertram <[email protected]>:

> I believe I see what is happening. During the auto-delete process the
> broker checks the address to see if it has any "bindings" (e.g. a queue).
> If so, it doesn't delete it. In the case of a retroactive address, there is
> a special divert binding which is part of what implements the retroactive
> functionality. Due to the presence of this divert, the broker will not
> auto-delete a retroactive address.
>
> I'm working on a fix now.
>
>
> Justin
>
> On Fri, Jan 9, 2026 at 6:46 PM Illia <[email protected]> wrote:
>
> > Hi Justin.
> > These are my configs:
> >
> >>           <address-setting match="singleValueQueue#">
> >>               <dead-letter-address>DLQ</dead-letter-address>
> >>               <expiry-address>ExpiryQueue</expiry-address>
> >>               <redelivery-delay>0</redelivery-delay>
> >>
> >>
> >>
> <message-counter-history-day-limit>10</message-counter-history-day-limit>
> >>               <address-full-policy>PAGE</address-full-policy>
> >>               <auto-create-queues>true</auto-create-queues>
> >>               <auto-create-addresses>true</auto-create-addresses>
> >>               <auto-delete-queues>true</auto-delete-queues>
> >>               <auto-delete-addresses>true</auto-delete-addresses>
> >>
> >> <auto-delete-queues-message-count>-1</auto-delete-queues-message-count>
> >>               <auto-delete-queues-delay>30000</auto-delete-queues-delay>
> >>
> >> <auto-delete-addresses-delay>60000</auto-delete-addresses-delay>
> >>
> >>
> <auto-delete-queues-skip-usage-check>true</auto-delete-queues-skip-usage-check>
> >>
> >>
> <auto-delete-addresses-skip-usage-check>true</auto-delete-addresses-skip-usage-check>
> >>
> >>               <default-last-value-queue>true</default-last-value-queue>
> >>               <default-last-value-key>lvqKey</default-last-value-key>
> >>               <default-non-destructive>true</default-non-destructive>
> >>               <retroactive-message-count>1</retroactive-message-count>
> >>
> >>               <!-- The size of each page file -->
> >>               <page-size-bytes>10M</page-size-bytes>
> >>
> >>               <!-- When we start applying the address-full-policy, e.g
> >> paging -->
> >>               <!-- Both are disabled by default, which means we will use
> >> the global-max-size/global-max-messages  -->
> >>               <max-size-bytes>-1</max-size-bytes>
> >>               <max-size-messages>-1</max-size-messages>
> >>
> >>               <!-- When we read from paging into queues (memory) -->
> >>
> >>               <max-read-page-messages>-1</max-read-page-messages>
> >>               <max-read-page-bytes>20M</max-read-page-bytes>
> >>
> >>               <!-- Limit on paging capacity before starting to throw
> >> errors -->
> >>
> >>               <page-limit-bytes>-1</page-limit-bytes>
> >>               <page-limit-messages>-1</page-limit-messages>
> >>           </address-setting>
> >>
> >
> > Addresses are not auto-removed with a retroactive-message-count config
> > set.
> > Here is what I see in Admin UI:
> > [image: image.png]
> > [image: image.png]
> > Thanks! Best regards.
> >
> > пт, 9 янв. 2026 г. в 05:53, Justin Bertram <[email protected]>:
> >
> >> Can you elaborate on the use-case where auto-delete-addresses isn't
> >> working?
> >>
> >>
> >> Justin
> >>
> >> On Thu, Jan 8, 2026 at 4:51 PM Illia <[email protected]> wrote:
> >>
> >> > Hi team,
> >> > Is there a way to auto-delete retroactive addresses?
> >> > Seems that auto-delete-addresses doesn't work.
> >> >
> >> > Thanks!
> >> >
> >>
> >
>

Reply via email to