Return-Path: 
 <ojb-dev-return-10044-apmail-db-ojb-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-ojb-dev-archive@www.apache.org
Received: (qmail 11569 invoked from network); 7 Sep 2004 14:40:17 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 7 Sep 2004 14:40:17 -0000
Received: (qmail 28469 invoked by uid 500); 7 Sep 2004 14:40:00 -0000
Delivered-To: apmail-db-ojb-dev-archive@db.apache.org
Received: (qmail 28321 invoked by uid 500); 7 Sep 2004 14:39:58 -0000
Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ojb-dev-unsubscribe@db.apache.org>
List-Subscribe: <mailto:ojb-dev-subscribe@db.apache.org>
List-Help: <mailto:ojb-dev-help@db.apache.org>
List-Post: <mailto:ojb-dev@db.apache.org>
List-Id: "OJB Developers List" <ojb-dev.db.apache.org>
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Delivered-To: mailing list ojb-dev@db.apache.org
Received: (qmail 28162 invoked by uid 99); 7 Sep 2004 14:39:57 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Received: from [217.205.133.130] (HELO srv002.hpd.co.uk) (217.205.133.130)
  by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 07 Sep 2004 07:39:55 -0700
Received: by SRV002 with Internet Mail Service (5.5.2657.72)
	id <SA18LPNL>; Tue, 7 Sep 2004 15:35:22 +0100
Message-ID: <6FB083FB72EFD21181D30004AC4CA18A04A0D322@SRV002>
From: Charles Anthony <charles.anthony@hpdsoftware.com>
To: OJB Developers List <ojb-dev@db.apache.org>
Subject: Distributed Lock Management
Date: Tue, 7 Sep 2004 15:35:21 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Hi All,

We're looking into making our application clustered. Well, actually, we
*are* making our application clustered (using multiple server processes
residing on multiple servers reading requests off a JMS queue). It looks
really rather cool.

What we need to do now is cope with distributed ODMG locking. I realise that
we have the Servlet LockMap which I shall certainly look at, but I have to
say, I'm a little concerned about having a single point of failure (which is
what I think would be the case - but please correct me if I'm wrong).

I am thinking of implementing a distributed LockMap using JMS, possibly on
top of activecluster.codehause.org - but has anyone got any pointers for me
for building lock managers/maps ? Other products/papers/discussions that I
can read up on ? Basically, from the OJB point of view, I think that the
thing to do is to create implement a new LockMap.

Cheers, 

Charles.


___________________________________________________________
HPD Software Ltd. - Helping Business Finance Business
Email terms and conditions: www.hpdsoftware.com/disclaimer 



---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org