You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (Closed) (JIRA)" <ji...@apache.org> on 2011/12/22 16:33:31 UTC

[jira] [Closed] (AMQ-3595) gcInactiveDestinations does not GC all queues

     [ https://issues.apache.org/jira/browse/AMQ-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-3595.
-----------------------------

    Resolution: Incomplete

This should be fixed in the 5.6 SNAPSHOT.  No test cases provided to very the users use-case.
                
> gcInactiveDestinations does not GC all queues
> ---------------------------------------------
>
>                 Key: AMQ-3595
>                 URL: https://issues.apache.org/jira/browse/AMQ-3595
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.0
>         Environment: CentOS 5.7, OpenJDK 1.6.0
>            Reporter: R.I.Pienaar
>
> Given the destination policy:
>         <destinationPolicy>
>           <policyMap>
>             <policyEntries>
>               <policyEntry queue="*.reply.>" gcInactiveDestinations="true" inactiveTimoutBeforeGC="120000" />
>             </policyEntries>
>           </policyMap>
>         </destinationPolicy>
> All matching queues are not being collected.  Most of my idle queues are being removed correctly:
> 2011-11-15 01:39:57,260 [etec] Scheduler] INFO  Queue                          - xx.reply.us.xx.net_10850 Inactive for longer than 120000 ms - removing ...
> But then others just sit and never get collected:
> $ activemq-admin query '-QQueue=*reply*us.xx*'|grep ^Name
> Name = xx.reply.us.xx.net_28319
> Name = xx.reply.us.xx.net_31184
> Looking at these in the JMX console there are no consumers, no producers, enqueued counts aren't increasing etc, they are idle by all information visible to me they are just not being removed.
> I am not sure what extra info I can provide but will gladly assist if you tell me what you need

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira