jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Müller" <thomas.muel...@day.com>
Subject Re: Repository locked by one server in clustered mode
Date Sat, 28 Jun 2008 19:47:06 GMT

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.


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 clustered
> 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 the
> 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 manage
> 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.

View raw message