Hi We had the same problem with NFS, I think it's an NFS/Java issue since there also seem to be problems with other applications. But someone told me they've it running successful with NFS, so I suppose it's NFS-implementation/version specific whether locking works or not (he ran a JVM 1.5.0_08 and RHEL 3/4 with NFS share on a NetApp SAN running NFS3).
Mario On 9/5/07, jdemic <[EMAIL PROTECTED]> wrote: > > Hey All, > > I'm attempting to setup activemq in a master/slave configuration as follows: > > http://activemq.apache.org/shared-file-system-master-slave.html > > I'm setting this up ontop of redhat es3 using the shared journal on an NFS > mount. When i start the slave, the following occurs: > > faultPersistenceAdapterFactory - Journal i locked... waiting 10 seconds for > the journal to be unlocked. > > This seems like the appopriate behavior (ie, the slave is spinning on the > lock waiting for it to be released.) The issue is, however, that activemq > exits after an hour and a half of so of attempting this. I'm not sure if > the issue is due to some interaction between java and nfs locking or an > issue with activemq. Curious if anyone else has experienced this. > > Thanks, > -jd > -- > View this message in context: > http://www.nabble.com/ActiveMQ-and-Linux-NFS-tf4384669s2354.html#a12499985 > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
