From users-return-18229-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Fri Mar 06 11:38:33 2009 Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 75726 invoked from network); 6 Mar 2009 11:38:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Mar 2009 11:38:33 -0000 Received: (qmail 21288 invoked by uid 500); 6 Mar 2009 11:38:30 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 21269 invoked by uid 500); 6 Mar 2009 11:38:29 -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 21258 invoked by uid 99); 6 Mar 2009 11:38:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Mar 2009 03:38:29 -0800 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.170 as permitted sender) Received: from [209.85.220.170] (HELO mail-fx0-f170.google.com) (209.85.220.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Mar 2009 11:38:19 +0000 Received: by fxm18 with SMTP id 18so330743fxm.38 for ; Fri, 06 Mar 2009 03:37:58 -0800 (PST) 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=whuBzr21B6UPBjll3Ra8AntZnKSIHt9pIFCaZJdq2Jo=; b=L4eGtM1abZTWJo14zjp0WvAPoZv0lU/5fjZXPZXFKNc3LWU6zaH5waCYzP+Z/zyeB4 lBlTXdjqUs38EKCG8+nODXdLaXRD8WrrhNhcZFcQsG2ar4DCRCaTzenQxRFAqx3BwiWz wYhIo1zeezeXJW0dn7UEDsSlnIyBoG/JoyrOY= 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=jjOHcX47Ki/uQkoXyrgk6KGGctaptJATw+d3oPPUW9eyGTxWqmiuLk2KTxv3fLqkLW K60kNPKKPVzVDzoOSJ91xiBeZGNz3YUZYUB2KIQSomu5uxTdl0dY1Qw18b1ws+k84O2M g8wXriZlL1W5m94o6BIwDT8J/oAPb10nVREKE= MIME-Version: 1.0 Received: by 10.181.208.11 with SMTP id k11mr768045bkq.19.1236339478735; Fri, 06 Mar 2009 03:37:58 -0800 (PST) In-Reply-To: <22345081.post@talk.nabble.com> References: <22345081.post@talk.nabble.com> Date: Fri, 6 Mar 2009 11:37:58 +0000 Message-ID: <3a73c17c0903060337y772e661ag3bc6f683754a9363@mail.gmail.com> Subject: Re: Transport disposed exceptions on shutdown From: Gary Tully To: users@activemq.apache.org Content-Type: multipart/alternative; boundary=001636c5a2b573aab5046471b767 X-Virus-Checked: Checked by ClamAV on apache.org --001636c5a2b573aab5046471b767 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Antony, You can safely ignore the DEBUG log messages and possibly the INFO message in the case as it occurs on shutdown. Typically INFO messages can be ignored as they will not effect reliabilty. However, I you can build a simple Junit test case that reliably reproduces this behavior, please open an jira issue and it can be investigated. There may some race condition in the VM transport that causes it to shutdown prematurly. Gary. 2009/3/5 Antsa > > I have an embedded broker started via a Spring ApplicationContext using the > activemq.xml file shipped with standard 5.2.0. > > When shutting down my Container and closing the Spring context, I get some > exceptions logged. The first is at DEBUG level > > 2009-03-05 15:25:20,765 DEBUG[VMTransport]: > org.apache.activemq.ActiveMQConnection [null] - Async exception with no > exception listener: > org.apache.activemq.transport.TransportDisposedIOException: Peer > (vm://localhost#1) disposed. > org.apache.activemq.transport.TransportDisposedIOException: Peer > (vm://localhost#1) disposed. > at > org.apache.activemq.transport.vm.VMTransport.iterate(VMTransport.java:203) > > and the second a short while later @INFO > > 2009-03-05 15:25:21,046 INFO [TossContainer]: > org.apache.activemq.AdvisoryConsumer [Container] - Failed to send remove > command: javax.jms.JMSException: Transport disposed. > javax.jms.JMSException: Transport disposed. > at > > org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62) > at > > org.apache.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1216) > at > > org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1208) > at > org.apache.activemq.AdvisoryConsumer.dispose(AdvisoryConsumer.java:56) > > I am assuming that as these are not any ERROR or WARNING logs they can be > ignored (??) but isn't having the INFO Exception stack trace a bit > unnecessary in an otherwise clean shutdown. > > Is there any way to disable this other than disabling INFO logging for this > class - If I do that will I lose something useful? > > Antony > > -- > View this message in context: > http://www.nabble.com/Transport-disposed-exceptions-on-shutdown-tp22345081p22345081.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source SOA http://FUSESource.com --001636c5a2b573aab5046471b767--