Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.co.uk;
  h=Received:X-YMail-OSG:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language;
  b=sVqPt1gF0cvvmuypL1F+CanuXpIpPkKA+JOgIJLvtarJl7b9Y2KanQHeeXCZdoaRnfmRvCRRR9ulFlJsYIjMBa58/8Vf9+h50oQ5zUe5qftdmo7uZ+sJlIbgL7+CggpH8/GKAFC9vVreTKEXskiMG1h4P3TJRhXRUqKTHGtIRQk=
  ;
From: "sbarriba" <sbarriba@yahoo.co.uk>
To: <users@jackrabbit.apache.org>
Subject: New workspaces are not clustered with LocalFileSystem
Date: Wed, 1 Aug 2007 21:27:54 +0100
Message-ID: <015a01c7d47a$71ca2400$555e6c00$@co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_015B_01C7D482.D38E8C00"
Thread-Index: AcfUenAR8dpNeCJTT4udKtYDbGNJbA==
Content-Language: en-gb

------=_NextPart_000_015B_01C7D482.D38E8C00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

We=92re continuing to tune our fault tolerant JackRabbit environment.

Thus far we have:

=B7        2 machines

=B7        Each running Tomcat 5.0.30 with JackRabbit 1.3 as a model 2 =
shared
resource

=B7        JackRabbit is configured with MySqlPersistenceManager,
LocalFileSystem and Database Journal

=B7        Each Tomcat node hosts an web application allowing users to
create/delete/edit JCR nodes. The web application also allows users to
create new workspaces.

=20

The problem we=92ve hit is that new workspaces are not clustered. =
Creating a
new workspace (Workspace2) on node A does not result in a new workspace
being created on node B e.g.

Node A file system:

=B7        Repository

o   Repository

o   Version

o   Workspaces

=A7  Workspace1

=A7  Workspace2

=20

Node B file system:

=B7        Repository

o   Repository

o   Version

o   Workspaces

=A7  Workspace1

This is problem for us as new workspaces are being created all the time,
hence they must be automatically clustered.=20

I=92m guessing this problem occurs as the =93create workspace=94 =
mechanism is
JackRabbit specific and is outside of the JCR spec and event model?

=20

Potential solutions:

=B7        Move to a DatabaseFileSystem =96 there are a couple of =
disadvantages
to this for us. We like to be able to view and amend the files and in
particular we regularly updated the custom_nodetypes.xml with new types =
as
part of an upgrade process. Presumably the nodes types would be less
accessible within the database.

=B7        Use a Network File Share for local files =96 we=92re trying =
to achieve
the simplest solution for fault tolerance therefore we=92d rather avoid =
the
complication of filesystem replication schemes (Linux DRBD etc) or the
expense of SAN solutions.

=B7        Manually create copy new workspaces =96 also not really an =
option as
new workspaces are created all the time

=20

All suggestions welcome.

Regards,

Shaun.


------=_NextPart_000_015B_01C7D482.D38E8C00--