Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 296BF65F5 for ; Thu, 16 Jun 2011 13:34:47 +0000 (UTC) Received: (qmail 80627 invoked by uid 500); 16 Jun 2011 13:34:46 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 80599 invoked by uid 500); 16 Jun 2011 13:34:46 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 80590 invoked by uid 99); 16 Jun 2011 13:34:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jun 2011 13:34:46 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of chubrilo@gmail.com designates 209.85.161.43 as permitted sender) Received: from [209.85.161.43] (HELO mail-fx0-f43.google.com) (209.85.161.43) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jun 2011 13:34:42 +0000 Received: by fxm3 with SMTP id 3so1483739fxm.2 for ; Thu, 16 Jun 2011 06:34:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Gm2/0NtGjg+hfaxtX/wBVk+2MbWSlafxtdAGGOIVV0U=; b=pKnfLPd2nFMBKUUJz4vVJbbpXWksmWyWHowc+U7edgzg1aZxzDLP9s39kU6Bu414PU ggEoB0o+vWwyX1jMhKUK/bflqRdlDwQbXnC6pPT+VDjrFfprkRdUb2igFcKBpFh6vdDR iZq/fzVB/nky4SC9UdBqMKhpc3lPI8QK/SFPQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=SoCBEeEtx9PWwnqM/XNQWZTvy2FOdyHIQ4ImyDaqm9Tch7JqFhxSVKR2c0f7YVzFU+ c31Io+FZAisZ4aenLG3beervDtmKQivXTivtNwAGM7uQoRCPSwvF12AIwiq+m7vATCQP u8Urt4HtilQU5g5WiztpUmRx2JOuDpZivBsJM= MIME-Version: 1.0 Received: by 10.223.21.7 with SMTP id h7mr1124803fab.72.1308231261101; Thu, 16 Jun 2011 06:34:21 -0700 (PDT) Sender: chubrilo@gmail.com Received: by 10.223.96.201 with HTTP; Thu, 16 Jun 2011 06:34:21 -0700 (PDT) In-Reply-To: References: Date: Thu, 16 Jun 2011 15:34:21 +0200 X-Google-Sender-Auth: bMPK7kBIUABtsi1PcpkO7riLd5g Message-ID: Subject: Re: How can I remove old queues without a java client? From: Dejan Bosanac To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=0015174412209a1e2104a5d453f8 --0015174412209a1e2104a5d453f8 Content-Type: text/plain; charset=ISO-8859-1 Yes, the inactivity means that there's 0 messages for some time and there are no new producers/consumers added Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Thu, Jun 16, 2011 at 2:45 PM, James Green wrote: > Now that's helpful... Let me just confirm my understanding: > > schedulePeriodForDestinationPurge="10000" > > Is telling the broker to delete inactive destinations every ten seconds? > > gcInactiveDestinations="true" inactiveTimoutBeforeGC="30000" > > Is expressing that the policyEntry should be garbage collected and should > be > considered garbase if inactive for 30 seconds or more? > > There's no definition of what precisely constitutes activity on that page. > Allow me to suggest: > > 1. A subscription to that destination > 2. A send to that destination > 3. A message being present on that destination > > How far off am I? I assume that a destination includes both queues and > topics? > > Thanks, > > James > > On 16 June 2011 09:04, Martin C. wrote: > > > Hi, > > > > Have a look at > > http://activemq.apache.org/delete-inactive-destinations.html > > This might be what you want. > > > > Best regards, > > Martin > > > > On Wed, Jun 15, 2011 at 11:00 PM, James Green > > wrote: > > > Not sure this is even possible? > > > > > > We dynamically create our queues by pushing messages to channels with > > > account numbers appended. They get read as the account reads from it's > > > queue. When that account goes dead and it's messages expired (or no > more > > get > > > pushed) we then end up with many queues doing nothing but taking up > space > > on > > > the web console. > > > > > > Is there perhaps a configuration directive to expire queues? I can't > see > > > anything in the STOMP protocol close to this. > > > > > > Thanks, > > > > > > James > > > > > > --0015174412209a1e2104a5d453f8--