activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-3595) gcInactiveDestinations does not GC all queues
Date Wed, 16 Nov 2011 21:49:52 GMT


Timothy Bish commented on AMQ-3595:

Would recommend you try your code using a 5.6 SNAPSHOT build as there's been so many fixes
there since 5.5.0.  If you still see a problem then creating a junit test case to reproduce
the issue is the next best step to take so we can have a means of reproducing the problem
and investigating it.
> gcInactiveDestinations does not GC all queues
> ---------------------------------------------
>                 Key: AMQ-3595
>                 URL:
>             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
> 2011-11-15 01:39:57,260 [etec] Scheduler] INFO  Queue                          -
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 =
> Name =
> 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
> 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:!default.jspa
For more information on JIRA, see:


View raw message