1 Reply Latest reply on May 10, 2010 10:41 AM by Luis Matos

    Can't get exclusive lock with windows clients (master/slave problem)

    Luis Matos Newbie

      We've been trying the last 2 days to get the master/slave configuration working.

       

      Setup:

       

      - 2 windows PCs with SUA and NFS client enabled. Windows clients support NFS 3.0;

      - NFS shared drive where the kahaDB is kept;

      - NFS sits on a Solaris 10, with NFS 4.0.

       

      The problem is, the master starts, and the slave also starts. We only have been able to make the slave stop if we work with master/slave in the same computer and working on the computer's filesystem (which is doof).

       

      Did anybody had/solved this problem?

       

      Thanks for any hint.

        • 1. Re: Can't get exclusive lock with windows clients (master/slave problem)
          Luis Matos Newbie

          Basically, we've been able to solve the issue using the servicemix lock - servicemix doesn't start when using the lock, so the embedded broker doesn't start either.

           

          One annoyance note though:

           

          we had to use:

           

          karaf.lock=true

          karaf.lock.dir=X:/nodeA

          karaf.lock.level=20

          karaf.lock.delay=10

           

          instead of

           

          servicemix.lock=true

          servicemix.lock.dir=X:/nodeA

          servicemix.lock.level=20

          servicemix.lock.delay=10

           

          because "servicemix" has been replaced by "karaf" on system.properties

           

          this wouldn't be so annoying if we didn't have to guess it by ourselves - we couldn't find anywhere where this was listed. But all is well when it's well.