[jira] [Created] (AMQ-3432) Slave broker able to start together with Master broker (shared file system master/slave setup)

["PK Tan (JIRA)" <ji...@apache.org>]

Slave broker able to start together with Master broker (shared file system master/slave setup)
----------------------------------------------------------------------------------------------

                 Key: AMQ-3432
                 URL: https://issues.apache.org/jira/browse/AMQ-3432
             Project: ActiveMQ
          Issue Type: Bug
          Components: Message Store
    Affects Versions: 5.5.0
         Environment: Windows 2003, Weblogic Application Server 
            Reporter: PK Tan
            Priority: Critical


When deploying activemq server in shared file system master/slave setup on a cluster of 2 servers without any of the MQ data files (journal folder, kr-store folder and lock file) [i.e. a fresh state], the slave broker is able to startup along with the master server. Both are active as verified by telnetting to the servers at the activemq port .  

If you were to restart both servers, both will not able to obtain the lock. If you stop both servers, delete the lock file and restart both the servers, we get back to the initial state where both servers are started and running (i.e. telnettable).

This issue might be related to AMQ-3273.  I'm logging another case for it because the environment and the situation is different . 



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira