Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 91535 invoked from network); 18 May 2007 16:08:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 May 2007 16:08:08 -0000 Received: (qmail 73925 invoked by uid 500); 18 May 2007 16:08:14 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 73709 invoked by uid 500); 18 May 2007 16:08:13 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 73699 invoked by uid 99); 18 May 2007 16:08:13 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 May 2007 09:08:13 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of james.strachan@gmail.com designates 66.249.82.226 as permitted sender) Received: from [66.249.82.226] (HELO wx-out-0506.google.com) (66.249.82.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 May 2007 09:08:05 -0700 Received: by wx-out-0506.google.com with SMTP id h29so945190wxd for ; Fri, 18 May 2007 09:07:44 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WgI3QYV+lv2J6hxyr2Ii8TEL37pbBUAkIQPPtSIQ1o3Wkf+UcKzVvnmV3fFrT6sqbcG7BWWnLPNwR187ahGuGvkZKZ6frwNG9eeIqI4TrS1qbmYFbEAMODC5X7PibSzIF0SFMfbaSS5IdF/UzfGV1JW87lkRxVsvimH4xI0fbdM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RPe+jiGZj8VJJOnioYgzw2JCyGXRBpmZNZ9Kw2KrZ+E6A859s2Y/0iugO0vw06KTgjxxw+UAf4cNWf99HG7WUJT5llfZls3xYLXsOiLXux9KQ5uon1D9Pr9O1PwCRUZXIc4ij22SyxZB4wU/DG8F2qHJLkWWT7FlrGkWQqqUyAM= Received: by 10.90.36.3 with SMTP id j3mr1975675agj.1179504463901; Fri, 18 May 2007 09:07:43 -0700 (PDT) Received: by 10.90.105.5 with HTTP; Fri, 18 May 2007 09:07:43 -0700 (PDT) Message-ID: Date: Fri, 18 May 2007 17:07:43 +0100 From: "James Strachan" To: users@activemq.apache.org Subject: Re: Shared File System Master Slave with OCFS In-Reply-To: <464DCB8B.20300@ldsys.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <10670741.post@talk.nabble.com> <464DCB8B.20300@ldsys.net> X-Virus-Checked: Checked by ClamAV on apache.org On 5/18/07, Christopher G. Stach II wrote: > James Strachan wrote: > > On 5/18/07, James Strachan wrote: > >> On 5/17/07, felipera wrote: > >> > Hi everyone, > >> > > >> > I am trying to setup two MQ Servers (4.1.1), sharing the same data > >> directory > >> > (I tried Derby and Kaha), on top of OCFS, but the locking doesn't > >> seem to be > >> > working. It works fine when both MQs are running on the same server > >> (still > >> > using OCFS). I see the second MQ waiting for the lock to be released > >> > ("Journal is locked... waiting 10 seconds for the journal to be > >> unlocked."). > >> > That's why I am not sure if it's a OCFS issue. But when I run each > >> MQ in > >> > separate boxes (still sharing the same data directory using OCFS) it > >> doesn't > >> > work, they both start successfully. > >> > >> This is the OCFS you're talking about right? > >> http://en.wikipedia.org/wiki/OCFS2 > > > > Actually OCFS2 seems more like a real distributed file system for > > general purpose use; the OCFS looks more specifically for using to > > host oracle data tables. Am wondering how good the file locking is on > > OCFS? Certainly its clear the mutex file locking from Java isn't > > supported on OCFS. > > > > OCFS2 properly supports POSIX locking semantics with fcntl. lockf and > flock aren't supported yet. If that's what the JVM uses under the > covers, you're out of luck. If this is about OCFS and not OCFS2, I'm > really sorry. :) Thanks for the heads up! :) I guess we could make the locking strategy pluggable & we could have some implementation call the fcntl locking. e.g. maybe using Jtux http://www.basepath.com/aup/jtux/ -- James ------- http://macstrac.blogspot.com/