From users-return-33462-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Sat Feb 2 05:24:06 2013 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 A153DEB7D for ; Sat, 2 Feb 2013 05:24:06 +0000 (UTC) Received: (qmail 83083 invoked by uid 500); 2 Feb 2013 05:24:06 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 82876 invoked by uid 500); 2 Feb 2013 05:24:05 -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 82839 invoked by uid 99); 2 Feb 2013 05:24:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Feb 2013 05:24:04 +0000 X-ASF-Spam-Status: No, hits=1.3 required=5.0 tests=URI_HEX X-Spam-Check-By: apache.org Received-SPF: unknown (nike.apache.org: error in processing during lookup of stephen.vincent@sas.com) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Feb 2013 05:23:57 +0000 Received: from [192.168.236.139] (helo=joe.nabble.com) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1U1VZb-0005gb-Mj for users@activemq.apache.org; Fri, 01 Feb 2013 21:23:31 -0800 Date: Fri, 1 Feb 2013 21:23:31 -0800 (PST) From: "Steve.V." To: users@activemq.apache.org Message-ID: <1359782611654-4662681.post@n4.nabble.com> Subject: How do you close orphaned consumers sometimes left when REST API clients are killed. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org If I abruptly kill my REST API client, I am sometimes left with an orphaned consumer over on the server. Aside from bouncing the server/broker, how do I kill those left-over consumers? The web admin interface doesn't seem to provide a way. ----- Stephen Vincent -- View this message in context: http://activemq.2283324.n4.nabble.com/How-do-you-close-orphaned-consumers-sometimes-left-when-REST-API-clients-are-killed-tp4662681.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.