Return-Path: Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org Received: (qmail 20733 invoked from network); 30 Aug 2010 06:24:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 30 Aug 2010 06:24:58 -0000 Received: (qmail 65340 invoked by uid 500); 30 Aug 2010 06:24:58 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 65088 invoked by uid 500); 30 Aug 2010 06:24:55 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 65079 invoked by uid 99); 30 Aug 2010 06:24:55 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Aug 2010 06:24:55 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [194.8.61.7] (HELO spamslammer1.tirol.gv.at) (194.8.61.7) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Aug 2010 06:24:33 +0000 From: =?iso-8859-1?Q?K=D6LL_Claus?= To: "users@jackrabbit.apache.org" Date: Mon, 30 Aug 2010 08:24:06 +0200 Subject: AW: Getting rid of Open-Scoped Locks without LockToken - Timeout? Thread-Topic: Getting rid of Open-Scoped Locks without LockToken - Timeout? Thread-Index: ActGDh9HN6Iw9KrVQT+xpGS+hcuwOQB/aVxA Message-ID: <89934884426A01458CBE55947B042D7219EC965312@EXCHMCA.tirol.local> References: <4C753FBD.3030905@mail.upb.de> In-Reply-To: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-cr-puzzleid: {83D3C305-588F-4BD2-84CC-CAE5908AE6ED} x-cr-hashedpuzzle: BX/Y BhlJ B762 CTDx DTqu Davw EoZ8 Eux4 FCcD FiU0 FjvR HGsu HSRB HhvG HxrS IoJI;1;dQBzAGUAcgBzAEAAagBhAGMAawByAGEAYgBiAGkAdAAuAGEAcABhAGMAaABlAC4AbwByAGcA;Sosha1_v1;7;{83D3C305-588F-4BD2-84CC-CAE5908AE6ED};YwAuAGsAbwBlAGwAbABAAHQAaQByAG8AbAAuAGcAdgAuAGEAdAA=;Mon, 30 Aug 2010 06:24:06 GMT;QQBXADoAIABHAGUAdAB0AGkAbgBnACAAcgBpAGQAIABvAGYAIABPAHAAZQBuAC0AUwBjAG8AcABlAGQAIABMAG8AYwBrAHMAIAB3AGkAdABoAG8AdQB0ACAATABvAGMAawBUAG8AawBlAG4AIAAtACAAVABpAG0AZQBvAHUAdAA/AA== acceptlanguage: de-DE, en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hi, see LockManager.lock(NodeImpl node, boolean isDeep, boolean isSessionScoped= , long timoutHint, String ownerInfo) where you can give a timoutHint. greets claus -----Urspr=FCngliche Nachricht----- Von: Neil Corbet [mailto:ncorbet@towerhillservices.com]=20 Gesendet: Freitag, 27. August 2010 19:34 An: users@jackrabbit.apache.org Betreff: Re: Getting rid of Open-Scoped Locks without LockToken - Timeout? Dominik Klaholt mail.upb.de> writes: >=20 > Hello, >=20 > I just wondered: What can I do if my application breaks in such an=20 > inconvenient way (e.g. hardware failure, or overlooked bug), that an=20 > open-scoped lock stays active? It seems, that locks do not time-out - is= =20 > there any way to get rid of locks without having the corresponding=20 > LockToken? Or will I never be able to acquire write access again? >=20 > Thanks > Dominik >=20 >=20 Dominik, I asked a similar question in the past to no avail. Looking through the code, I think it gets the nodes itemID and then does some=20 extra-magic on it to create the token. I think you could re-create this code. I think jackrabbit 2.0 makes it a little easier.=20 But, I am curious what others do about this problem. So, I am=20 giving this question a little bump with a reply. :) Neil =20