From users-return-18965-apmail-activemq-users-archive=activemq.apache.org@activemq.apache.org Tue May 05 19:14:56 2009 Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 21705 invoked from network); 5 May 2009 19:14:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 May 2009 19:14:56 -0000 Received: (qmail 27748 invoked by uid 500); 5 May 2009 19:14:55 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 27709 invoked by uid 500); 5 May 2009 19:14:54 -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 27699 invoked by uid 99); 5 May 2009 19:14:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2009 19:14:54 +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, 05 May 2009 19:14:45 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1M1Q2t-0004Wa-1S for users@activemq.apache.org; Tue, 05 May 2009 12:11:15 -0700 Message-ID: <23394015.post@talk.nabble.com> Date: Tue, 5 May 2009 12:11:15 -0700 (PDT) From: icfantv To: users@activemq.apache.org Subject: JDBC master/slave runtime issue MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: adam.gordon@readytalk.com X-Virus-Checked: Checked by ClamAV on apache.org We're running activeMQ in a master/slave configuration with a JDBC data store and two brokers in a failover configuration. According to the logs, everything is happy. The behavior we're seeing is that, in testing, when we kill the master the slave takes over (as designed, and the log file shows this), but our java code sporadically doesn't detect that the slave has taken over and the code will just sit there blocking waiting (as if to be notified) that the broker is back up. What's really weird is that this is sporadic. Sometimes it all works ok, and sometimes it doesn't work. Anyone have any ideas as to what might be going on? We're running two brokers on the same server but on different ports (both for the service and jetty) and things are essentially ok, save for the apparent random failed reconnect. Thanks, --adam -- View this message in context: http://www.nabble.com/JDBC-master-slave-runtime-issue-tp23394015p23394015.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.