Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 51610 invoked from network); 22 Oct 2010 17:23:48 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Oct 2010 17:23:48 -0000 Received: (qmail 88156 invoked by uid 500); 22 Oct 2010 17:23:48 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 88111 invoked by uid 500); 22 Oct 2010 17:23:47 -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 88098 invoked by uid 99); 22 Oct 2010 17:23:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Oct 2010 17:23:47 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of joe.niski@nwea.org designates 216.32.180.16 as permitted sender) Received: from [216.32.180.16] (HELO VA3EHSOBE009.bigfish.com) (216.32.180.16) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Oct 2010 17:23:41 +0000 Received: from mail161-va3-R.bigfish.com (10.7.14.242) by VA3EHSOBE009.bigfish.com (10.7.40.29) with Microsoft SMTP Server id 14.1.225.8; Fri, 22 Oct 2010 17:23:20 +0000 Received: from mail161-va3 (localhost.localdomain [127.0.0.1]) by mail161-va3-R.bigfish.com (Postfix) with ESMTP id B73D61202DC for ; Fri, 22 Oct 2010 17:23:19 +0000 (UTC) X-SpamScore: -36 X-BigFish: VS-36(zzbb2dKbb2cK1432N9370J98dN4015Le66R9371Pzz1202hzz8275bh8275dh238anz31h27ah2a8h61h) X-Spam-TCS-SCL: 0:0 X-Forefront-Antispam-Report: KIP:(null);UIP:(null);IPVD:NLI;H:lko-exh01.Americas.nwea.pvt;RD:error;EFVD:FOP Received: from mail161-va3 (localhost.localdomain [127.0.0.1]) by mail161-va3 (MessageSwitch) id 128776819994274_21558; Fri, 22 Oct 2010 17:23:19 +0000 (UTC) Received: from VA3EHSMHS036.bigfish.com (unknown [10.7.14.235]) by mail161-va3.bigfish.com (Postfix) with ESMTP id 0B736DC0058 for ; Fri, 22 Oct 2010 17:23:19 +0000 (UTC) Received: from lko-exh01.Americas.nwea.pvt (70.98.171.6) by VA3EHSMHS036.bigfish.com (10.7.99.46) with Microsoft SMTP Server (TLS) id 14.1.225.8; Fri, 22 Oct 2010 17:23:17 +0000 Received: from LKO-EXCH01.Americas.nwea.pvt ([10.1.1.120]) by lko-exh01.Americas.nwea.pvt ([10.1.0.124]) with mapi; Fri, 22 Oct 2010 10:23:16 -0700 From: Joe Niski To: "users@activemq.apache.org" Date: Fri, 22 Oct 2010 10:23:14 -0700 Subject: Re: Help destroying 1,000+ subscribers Thread-Topic: Help destroying 1,000+ subscribers Thread-Index: ActyDc+OuRBgDAnxS+Sxu58uDnSkSQ== Message-ID: <4CC1C882.8010500@nwea.org> References: <4CC07612.40805@nwea.org> In-Reply-To: Reply-To: Joe Niski Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9pre) Gecko/20100217 Lightning/1.0b1 Shredder/3.0.3pre acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_4CC1C8828010500nweaorg_" MIME-Version: 1.0 X-Bypass-Agent: EF-1; X-OriginatorOrg: nwea.org --_000_4CC1C8828010500nweaorg_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable (James, i'm replying to the list - your reply came directly to me) The behavior i've noticed is that if the end consumer is outside of ActiveM= Q (e.g., an MDB on a Java EE server, rather than a Camel route configured i= n activemq.xml), AND the consumer is not running when ActiveMQ starts up, t= he durable subscriptions don't show up in the console. Joe Niski IS Development | NWEA PHONE 503.212.3382 | FAX 503.639.7873 NWEA.ORG<3D%22http://www.nwea.org/%22> | Partnering to Help All Kids Lear= n On 10/22/2010 12:51 AM, James Green wrote: We are reliant on persistent messages lasting up to 3 days. Interestingly I decided to restart AMQ on the test machine which had > 1,000 subscribers and when it came back up the web interface showed they had all disappeared. Does this mean AMQ will not persist a durable subscriber across a restart? James On 21 October 2010 18:19, Joe Niski wrote: > The only way i've discovered to remove "zombie" durable subscribers (they > were once subscribed, but will never reconnect again) is to delete the > data-store directory. Harsh, and probably not a good idea in a production > environment unless you can guarantee there are no in-flight persistent > messages when you take ActiveMQ down. > > Joe Niski > IS Development | NWEA > > PHONE 503.212.3382 | FAX 503.639.7873 > > NWEA.ORG | Partnering to Help All Kids Learn > > On 10/21/2010 08:55 AM, James Green wrote: > > Hi, > > Due to a bug my side I've managed to create over 1,000 durable topic > subscribers each with differing client-ids. Yep, that equals quite a > mess. > > Somehow I need to unsubscribe these guys. Each was created by the same > PHP script being invoked repeatedly overnight. > > I have created a script that identifies itself as a subscribed > client-id, subscribes to the topic and immediately unsubscribes from > it, however the web interface still shows a subscription for it. The > "Delete" button also merely reloads the page which seems like quite a > bug too... > > I have stomp-level logging switched on and clearly see the client > connecting with the correct ID, and the unsubscribe command for the > right topic coming in. There's no response to this however, should > there be? > > Can anyone advise on what I need to do? AMQ 5.4.0 in use on this > particular instance... > > Thanks, > > James > > --_000_4CC1C8828010500nweaorg_--