Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 60155 invoked from network); 9 Jun 2007 12:09:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Jun 2007 12:09:03 -0000 Received: (qmail 23859 invoked by uid 500); 9 Jun 2007 12:09:06 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 23826 invoked by uid 500); 9 Jun 2007 12:09:06 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 23817 invoked by uid 99); 9 Jun 2007 12:09:06 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Jun 2007 05:09:06 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Jun 2007 05:09:01 -0700 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1HwzkH-0003xN-3H for dev@activemq.apache.org; Sat, 09 Jun 2007 05:08:41 -0700 Message-ID: <11039806.post@talk.nabble.com> Date: Sat, 9 Jun 2007 05:08:40 -0700 (PDT) From: Maxim Butov To: dev@activemq.apache.org Subject: Re: Probable bug. In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: mbutov@gmail.com References: <10968768.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Hiram, the configuration is following (I took it from an example): Regards, Maxim Hiram Chirino wrote: > > For the stack trace it looks normal. ActiveMQ is waiting for a > response from the broker which may take a while. If it takes forever, > it would be interesting to find out if the broker is remote or if the > vm:// transport is being used. > > Another way to resolve this is to have the Spring > DefaultMessageListenerContainer use a deamon thread. Not sure if > there is a way to configure that. > > Regards, > Hiram > -- View this message in context: http://www.nabble.com/Probable-bug.-tf3871562s2354.html#a11039806 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.