[
https://issues.apache.org/jira/browse/AMQ-9692?focusedWorklogId=1001704&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1001704
]
ASF GitHub Bot logged work on AMQ-9692:
---------------------------------------
Author: ASF GitHub Bot
Created on: 24/Jan/26 18:57
Start Date: 24/Jan/26 18:57
Worklog Time Spent: 10m
Work Description: mattrpav commented on PR #1484:
URL: https://github.com/apache/activemq/pull/1484#issuecomment-3795354513
@cshannon new DestinationIsActiveTest adds parameterized tests for logical
combinations of:
PolicyEntry gc flag combinations vs status of:
1. Normal consumer
2. Network consumer
3. Wildcard consumer
There is also a fail-safe check to ensure parameter config is solid to
verify that anytime the normal app consumer is active, the queue is flagging as
active.
Intellij confirmed 100% branch coverage on those methods (aside from the
producer count test)
Issue Time Tracking
-------------------
Worklog Id: (was: 1001704)
Time Spent: 2h 10m (was: 2h)
> Support destination gc sweep of destinations with wild card consumers
> ---------------------------------------------------------------------
>
> Key: AMQ-9692
> URL: https://issues.apache.org/jira/browse/AMQ-9692
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Minor
> Fix For: 6.3.0, 5.19.2
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Currently, a wild-card consumer can hold up a destination from being
> automatically garbage collected. This change would add a policyEntry setting
> to allow garbage collection if the destination only has wild card consumers
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
