Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 26970 invoked from network); 18 Mar 2009 16:54:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Mar 2009 16:54:45 -0000 Received: (qmail 62121 invoked by uid 500); 18 Mar 2009 16:54:45 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 61703 invoked by uid 500); 18 Mar 2009 16:54:44 -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 61692 invoked by uid 99); 18 Mar 2009 16:54:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Mar 2009 09:54:44 -0700 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates 209.85.220.174 as permitted sender) Received: from [209.85.220.174] (HELO mail-fx0-f174.google.com) (209.85.220.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Mar 2009 16:54:34 +0000 Received: by fxm22 with SMTP id 22so145432fxm.38 for ; Wed, 18 Mar 2009 09:54:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=wUueOGxBvH74yf3k2Az3OxZkhX6WkloGlT/dwZK+idk=; b=PsfUL++CW2LUUm8WBSInCP3JLv2jvuPQ1WLCvfbJi9taee66EEIl/3IKJRDUHu0Fhc Sxn3Uo8/8swgqJcladWLsrv/ccLi0QGgeJFXMp1YqqCKCPgAJMJtVyi660VIZ1mB/EzA X9Nlm2MrQAf+HgSfVjmcg41GaRFhbY+Az4RJs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=H5AauSsubFzftY/ouFozK1p44LirgeXLNMryLWkK0OLyqPiyUW/B4LL73PPJZaGcRL uJuunByBohc/S+ROEBrjZRrKQv1GuXKP+tiWC2sf5GVqIOtqk+bQPZ9sFy+K5gl4OSlH bLmEwTLI1huWQK+HiY4O0O2I4UCIHGth+8Ze4= MIME-Version: 1.0 Received: by 10.204.76.13 with SMTP id a13mr478197bkk.105.1237395253345; Wed, 18 Mar 2009 09:54:13 -0700 (PDT) In-Reply-To: <22576446.post@talk.nabble.com> References: <22576446.post@talk.nabble.com> Date: Wed, 18 Mar 2009 16:54:13 +0000 Message-ID: <3a73c17c0903180954x54d017e9t2f2c0246ba4c3176@mail.gmail.com> Subject: Re: Killing activemq with connected JMS listener From: Gary Tully To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=001485f91c3085bee40465678899 X-Virus-Checked: Checked by ClamAV on apache.org --001485f91c3085bee40465678899 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit If this is 5.2, and you do not provide a brokerUrl to your activemq connection factory then the failover transport will be used by default and it will block waiting to reconnect. Provide a brokerUrl and use "tcp://..." and you will get the exception you require. 2009/3/18 mffrench > > Hello, > > if I kill ActiveMQ, there is no exception raised to my connected JMS > listener and so my client doesn't detect the link is broken with ActiveMQ. > I > think this is a bug which should be corrected. Is there any issue about > this > ? > > Thanks > -- > View this message in context: > http://www.nabble.com/Killing-activemq-with-connected-JMS-listener-tp22576446p22576446.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source SOA http://FUSESource.com --001485f91c3085bee40465678899--