[ 
https://issues.apache.org/jira/browse/AMQ-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13151557#comment-13151557
 ] 

R.I.Pienaar commented on AMQ-3595:
----------------------------------

Is there a rough ETA for 5.6 being released?
                
> 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

        

Reply via email to