Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: "Seidel. Robert" <Robert.Seidel@aeb.de>
To: "users@jackrabbit.apache.org" <users@jackrabbit.apache.org>
Date: Tue, 16 Nov 2010 08:51:59 +0100
Subject: AW: Multiple instances of repository
Thread-Topic: Multiple instances of repository
Thread-Index: AcuFYH3L7Fi2pRn8RfOrnn/Kfiz93gAAUEoQ
Message-ID: <C95151191D741844A776DE94864A68AA107B2B50B9@S-HQMX7.pmbelz.de>
References: <2DD29CC841489C44A6E38A6CA5D4BB270D75C5F034@emcexc-02>
In-Reply-To: <2DD29CC841489C44A6E38A6CA5D4BB270D75C5F034@emcexc-02>
Accept-Language: de-DE
Content-Language: de-DE
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Nikhil,

if you want to use clustering, you have to define a repository home for eac=
h cluster.=20

Clustering is necessary, if you want to have the same data/indexes at all c=
luster nodes - the key word is synchronization.

If your instances and the repositories operate separately from each other, =
you don't need clustering. Separate repository homes, data stores and persi=
stence managers will do the job.

Kindly regards, Robert

-----Urspr=FCngliche Nachricht-----
Von: nikhil.agrawal@emeter.com [mailto:nikhil.agrawal@emeter.com]=20
Gesendet: Dienstag, 16. November 2010 08:33
An: users@jackrabbit.apache.org
Betreff: Multiple instances of repository

Hi,

I am using jackrabbit as JCR implementation in my project. I am running jac=
krabbit with in my application in the same jvm.
The application read the content from repository and also writes some conte=
nt in repository.
There could be multiple concurrent instances of my application running on t=
he same or different machines.
I have a configuration file for jackrabbit and I have a single repository h=
ome for jackrabbit.
Now as soon as one instance of the application is up and running, I can't r=
un the other instance as the first instance creates a lock file in reposito=
ry home.
After doing some search I came to know about running the jackrabbit in clus=
tered mode.
Now my question is even in this case I will have to specify a different rep=
ository home for every run, right?
That means I should form the repository home path at the run time because a=
t compile time I am not sure how many instance will be run.
This is a standalone java application and theoretically n number of instanc=
e can be run.
My question is when I have to specify a different repository path for every=
 run, then the jackrabbit will work even with out clustering?
Because .lock file will be different for different runs as the repository h=
ome is different.
I know I am missing something here, please help me.
I am attaching my conf file with this mail.

Thanks,
Nikhil