Return-Path: Delivered-To: apmail-geronimo-activemq-users-archive@www.apache.org Received: (qmail 73416 invoked from network); 12 Dec 2006 17:15:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Dec 2006 17:15:28 -0000 Received: (qmail 54587 invoked by uid 500); 12 Dec 2006 17:15:36 -0000 Delivered-To: apmail-geronimo-activemq-users-archive@geronimo.apache.org Received: (qmail 54380 invoked by uid 500); 12 Dec 2006 17:15:36 -0000 Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-users@geronimo.apache.org Delivered-To: mailing list activemq-users@geronimo.apache.org Received: (qmail 54369 invoked by uid 99); 12 Dec 2006 17:15:36 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2006 09:15:36 -0800 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 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Dec 2006 09:15:24 -0800 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1GuBDc-0004iK-1B for activemq-users@geronimo.apache.org; Tue, 12 Dec 2006 09:15:04 -0800 Message-ID: <7837334.post@talk.nabble.com> Date: Tue, 12 Dec 2006 09:15:03 -0800 (PST) From: Anthrope To: activemq-users@geronimo.apache.org Subject: Re: JDBC Master Slave In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: pn@anthrope.com References: <7790142.post@talk.nabble.com> <7790329.post@talk.nabble.com> <7790449.post@talk.nabble.com> <7833488.post@talk.nabble.com> <7835874.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org Something is surely nor right. The logical sequence should be that the broker first attempt to acquire the lock before starting any services. My config file is exactly what is specified in the example, and the behaviour I see is not what I should be. Has anyone actually got this configuration to work? As regards the client dying, the only information I have is that a JMSException occurred. I'd have posted other information if I'd had it. James.Strachan wrote: > > On 12/12/06, Anthrope wrote: >> >> James, >> Thanks for the response. I am using the config file as-is from the >> example. I am using the jdbcPersistenceAdapter element, and here's what I >> have: >> >> - I start activemq on port 5616 and it duly starts up, taking over as the >> master >> - I start a second instance with exactly the same configuration, and it >> fails to start, because it tries to bind to 5616 >> - I change the configuration to use port 5626, > > This sounds like something is not working correctly as a slave should > not try to bind to a socket until it becomes the master. > >> - I don't quite understand how both end up becoming the master, but >> perhaps >> it's just how it's being logged? > > No - sounds like you're not using a shared database between the two. > > >> - I kill the master broker and then run the consumer example with the >> failover uri and am able to successfully extract about 7800 messages >> before >> the client shuts down with a JMS exception > > What exception? > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/JDBC-Master-Slave-tf2792225.html#a7837334 Sent from the ActiveMQ - User mailing list archive at Nabble.com.