Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <18177897.post@talk.nabble.com>
Date: Sat, 28 Jun 2008 23:53:48 -0700 (PDT)
From: Balak Dev <balaforums@gmail.com>
To: dev@jackrabbit.apache.org
Subject: Re: Repository locked by one server in clustered mode
In-Reply-To: <91f3b2650806281247w7bb6d922r27edc6e1ef4be4e8@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <18170869.post@talk.nabble.com>
 <91f3b2650806281247w7bb6d922r27edc6e1ef4be4e8@mail.gmail.com>


Hi Thomas,

Thanks for the reply.

I had a look at the link which you have provided. It had very good
information in it. However the point that i didnt understand overhere is:

1) Is there any relation between the managed server [Cluster node] and the
cluster id which we are mentioning?

2) If not then where are we mentioning that this cluster configuration is
for this managed server [Cluster node] ?

Thanks,
Bala.


Thomas M=C3=BCller-2 wrote:
>=20
> Hi,
>=20
> When using clustering, the cluster nodes can not share the repository.
> Each cluster node must have its own repository configuration.
> See http://wiki.apache.org/jackrabbit/Clustering for details.
>=20
> Regards,
> Thomas
>=20
> On Sat, Jun 28, 2008 at 3:44 PM, Balak Dev <balaforums@gmail.com> wrote:
>>
>> Dear All,
>>                  We have been facing a problem from few days. Struggled =
a
>> lot but didn't get the solution. We have two managed servers in clustere=
d
>> mode. When one of the servers get started, it locks the repository and
>> doesn't release it. So the second manage server is not able to access th=
e
>> repository and thus the rules.
>>
>> Therefore if any of the users request goes to the managed server 1, then
>> we
>> don't have any issues as the rules are accessible to it. But if the
>> request
>> goes to the manage server 2, then the user screen hangs up, as the manag=
e
>> server 2 isn't able to access the repository.
>>
>> The following is the error we have captured from the console:
>>
>> The repository home at /home/weblogic/bea/u
>> ser_projects/domains/MUTLI_INSTANCE_DOMAIN/repository appears to be in
>> use
>> since the file at /home/weblogic/bea/u
>> ser_projects/domains/MUTLI_INSTANCE_DOMAIN/repository/.lock is locked by
>> another process.
>>
>> Any help on this is appreciable.
>>
>> Thanks,
>> Bala.
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Repository-locked-by-one-server-in-clustered-mode-=
tp18170869p18170869.html
>> Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
>>
>>
>=20
>=20

--=20
View this message in context: http://www.nabble.com/Repository-locked-by-on=
e-server-in-clustered-mode-tp18170869p18177897.html
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.