Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 66358 invoked from network); 28 Jun 2008 19:49:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Jun 2008 19:49:01 -0000 Received: (qmail 53186 invoked by uid 500); 28 Jun 2008 19:49:01 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 53150 invoked by uid 500); 28 Jun 2008 19:49:01 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 53139 invoked by uid 99); 28 Jun 2008 19:49:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Jun 2008 12:49:01 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tmueller@day.com designates 62.192.10.254 as permitted sender) Received: from [62.192.10.254] (HELO goobak01.day.com) (62.192.10.254) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Jun 2008 19:48:09 +0000 Received: by goobak01.day.com (Postfix, from userid 1212) id 74A1450838; Sat, 28 Jun 2008 21:47:14 +0200 (CEST) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by goobak01.day.com (Postfix) with ESMTP id 0610F5082E for ; Sat, 28 Jun 2008 21:47:13 +0200 (CEST) Received: by yw-out-2324.google.com with SMTP id 3so519066ywj.31 for ; Sat, 28 Jun 2008 12:47:06 -0700 (PDT) Received: by 10.151.143.3 with SMTP id v3mr4858314ybn.244.1214682426615; Sat, 28 Jun 2008 12:47:06 -0700 (PDT) Received: by 10.151.84.3 with HTTP; Sat, 28 Jun 2008 12:47:06 -0700 (PDT) Message-ID: <91f3b2650806281247w7bb6d922r27edc6e1ef4be4e8@mail.gmail.com> Date: Sat, 28 Jun 2008 21:47:06 +0200 From: "=?ISO-8859-1?Q?Thomas_M=FCller?=" Sender: tmueller@day.com To: dev@jackrabbit.apache.org Subject: Re: Repository locked by one server in clustered mode In-Reply-To: <18170869.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <18170869.post@talk.nabble.com> X-Google-Sender-Auth: 61f37a957415bbca X-Virus-Checked: Checked by ClamAV on apache.org Hi, 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. Regards, Thomas On Sat, Jun 28, 2008 at 3:44 PM, Balak Dev 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. > >