Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <26729676.post@talk.nabble.com>
Date: Thu, 10 Dec 2009 07:52:00 -0800 (PST)
From: MrBen <mbunn@smart421.com>
To: users@activemq.apache.org
Subject: Master - slave not working
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


I've got two solaris servers, and want a broker running on each with a
corresponding slave on the opposite server. I'm using AMQ Persistence I've
got a NAS that is mounted on both and have used the same filesystem location
for the master/slave pair. However, master starts up fine, but when i start
up the slave it just grabs the lock off the the master and starts up itself. 

When i kill the master i get a java.io.IOException: Stale NFS file handle.

What makes it even more strange to me is that if i start the brokers up in
the reverse order i get the normal:
WARN  AMQPersistenceAdapter          - Waiting to Lock the Store 


I'm on ActiveMQ 5.3.0.5
-- 
View this message in context: http://old.nabble.com/Master---slave-not-working-tp26729676p26729676.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.