Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: message received from 54.164.171.186
 which is an MX secondary for users@activemq.apache.org)
Date: Mon, 27 Apr 2015 22:24:28 -0700 (PDT)
From: khandelwalanuj <khandelwal.anuj90@gmail.com>
To: users@activemq.apache.org
Message-ID: <1430198668394-4695731.post@n4.nabble.com>
In-Reply-To: 
 <CAPVVMa_Pm-g29GJ9GDBvx9uqDRo1hhcdaQXbB=L0UsAF+vwxWQ@mail.gmail.com>
References: <1430120112280-4695677.post@n4.nabble.com>
 <1430120338525-4695678.post@n4.nabble.com>
 <CAPVVMa_Pm-g29GJ9GDBvx9uqDRo1hhcdaQXbB=L0UsAF+vwxWQ@mail.gmail.com>
Subject: Re: ActiveMQ master-slave topology issue[BUG]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

I got the logs in this order only and after further checking the system I
got to know that NFS(where we put kahadb and broker logs) was slow during
that time.

I can understand the delay in logs or I/O operations are slow during that
time but it does not justify why failover also open it's transport
connector. 

The main concern here is that the (master-slave-shared-storage)topology is
broken which should not happen in any case. If I/O operations are not
happening, master broker should stop and let the failover serve the clients
but here master didn't stop and both opened the connector. 

Thanks,
Anuj


--
View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-master-slave-topology-issue-BUG-tp4695677p4695731.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.