[
https://issues.apache.org/jira/browse/AMQ-3339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3339.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
Assignee: Timothy Bish
Fixed in trunk, adds option maxPurgedDestinationsPerSweep to BrokerService to
control the number of destinations that can be purged in a single scan, if the
value is 0 or less then the purge amount is unbounded.
> Allow for an option to bound the number of GC'd Destinations when using
> gcInactiveDestinations=true
> ---------------------------------------------------------------------------------------------------
>
> Key: AMQ-3339
> URL: https://issues.apache.org/jira/browse/AMQ-3339
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.4.2, 5.5.0
> Environment: N/A
> Reporter: Joshua Watkins
> Assignee: Timothy Bish
> Priority: Minor
> Labels: gcInactiveDestinations
> Fix For: 5.6.0
>
>
> When gcInactiveDestinations=true there is the situation where many (1000's)
> inactive destinations are all garbage collected at the same time. This can
> adversely affect the performance of the broker. It would be nice to have the
> ability to set a maximum number of destinations to remove per sweep (e.g.
> maxGCDestinationsPerSweep=500).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
