activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eden Chen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMQ-4497) Shared File System Master/Slave function broken with NFSv4 after network back stable
Date Tue, 30 Apr 2013 07:42:17 GMT
Eden Chen created AMQ-4497:
------------------------------

             Summary: Shared File System Master/Slave function broken with NFSv4 after network
back stable
                 Key: AMQ-4497
                 URL: https://issues.apache.org/jira/browse/AMQ-4497
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.5.1
         Environment: NFSv4
            Reporter: Eden Chen


In the experiment, I used kahaDB to be the persistenceAdapter. 
The setting is like: 
<persistenceAdapter>
  <kahaDB directory="/nfs4/server/data/kahadb"/>
</persistenceAdapter>
There are 2 brokers in different machines, and the NFS server is installed in one of the machines.
 
I will use "broker1" to present the one without out NFS server and "broker2" for the other
one. 

I start broker1 earlier then brokerQ2, so the broker1 grab the file lock and be the master,
broker2 be slave brokers and sit in a loop trying to grab the lock from the master broker.

Then I disconnect broker1's network, broker2 can grab the file lock and start working after
a while, Broker1 is still alive and don't show any error message. 
After broker2 starting working, I enable broker1's network, both broker1 and broker2 can serve
client's request at the same time (I can use webconsole to send message for both brokers).


Both master and slave broker can grab the same file lock and receive client's request, this
can cause losing message or restart AMQ failed. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message