5 Replies Latest reply on Jun 26, 2012 10:11 AM by Justin Bertram

    Shared File System Master Slave

    Ameem Shaik Newbie

      In the following link, ActiveMQ has a NFSv3 warning about some locking issues that essentially renders the data in the shared file system inaccessbile to the slave node. If I understand correctly, when the master node is abnormally terminated, it does not release the lock on the file system, after which the slave cannot obtain it.




      Since HornetQ also uses a shared file system, I would like to know whether it has avoided this problem or not. If it has, how exactly has it accomplished this? It makes me nervous that ActiveMQ has openly stated this problem exists, so I would like to know if HornetQ has solved this somehow.