Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 5327 invoked from network); 15 Sep 2009 18:21:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Sep 2009 18:21:15 -0000 Received: (qmail 41236 invoked by uid 500); 15 Sep 2009 18:21:15 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 41212 invoked by uid 500); 15 Sep 2009 18:21:14 -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 41202 invoked by uid 99); 15 Sep 2009 18:21:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Sep 2009 18:21:14 +0000 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 (nike.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; Tue, 15 Sep 2009 18:21:04 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Mncdv-0005oW-31 for users@activemq.apache.org; Tue, 15 Sep 2009 11:20:43 -0700 Message-ID: <25458935.post@talk.nabble.com> Date: Tue, 15 Sep 2009 11:20:43 -0700 (PDT) From: dbczak To: users@activemq.apache.org Subject: Re: Persistence Behavior In-Reply-To: <25458903.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: zak@dbconcert.com References: <25458903.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org OK, I was able to stop it from waiting forever by setting the maxReconnectAttempts setting. However, it still does not behave as expected. Once everything is up and running, I shut down one of the consumers. In the producer I get this error: DEBUG - Transport failed with the following exception:java.io.EOFException DEBUG - Attempting connect to: tcp://localhost:61616 DEBUG - Connect fail to: tcp://localhost:61616, reason: java.net.ConnectException: Connection refused: connect ERROR - Failed to connect to transport after: 1 attempt(s) DEBUG - Async exception with no exception listener: java.net.ConnectException: Connection refused: connect Then, every 10 seconds I get these messages: DEBUG - 10000 ms elapsed since last write check. DEBUG - Message sent since last write check, resetting flag When the producer tries to send a message, we get this error. (Shouldn't this just store the peristed message): ERROR - Exception caught: javax.jms.JMSException: Connection refused: connect And finally, when I bring up the crashed consumer, nothing happens. It does not get the missed messages, and the producer continues to print out the same message every 10 seconds. Please help. -- View this message in context: http://www.nabble.com/Persistence-Behavior-tp25458903p25458935.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.