From jackrabbit-dev-return-3292-apmail-incubator-jackrabbit-dev-archive=www.apache.org@incubator.apache.org Tue Aug 23 14:12:12 2005 Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 33053 invoked from network); 23 Aug 2005 14:12:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Aug 2005 14:12:12 -0000 Received: (qmail 77721 invoked by uid 500); 23 Aug 2005 14:12:10 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 77705 invoked by uid 99); 23 Aug 2005 14:12:10 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Aug 2005 07:12:09 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 1C939123 for ; Tue, 23 Aug 2005 16:12:09 +0200 (CEST) Message-ID: <1850312119.1124806329115.JavaMail.jira@ajax.apache.org> Date: Tue, 23 Aug 2005 16:12:09 +0200 (CEST) From: "Dominique Pfister (JIRA)" To: jackrabbit-dev@incubator.apache.org Subject: [jira] Resolved: (JCR-194) dead lock while locking or unlocking nodes In-Reply-To: <235806849.1124722928353.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JCR-194?page=all ] Dominique Pfister resolved JCR-194: ----------------------------------- Fix Version: 1.0 Resolution: Fixed Another concurrency issue: whereas deadlock has now been removed, two competing threads, locking and unlocking at about the same time could invalidate each other's node representation. Thanks again to Walter Raboch for finding this issue. Fixed in r239410. > dead lock while locking or unlocking nodes > ------------------------------------------ > > Key: JCR-194 > URL: http://issues.apache.org/jira/browse/JCR-194 > Project: Jackrabbit > Type: Bug > Components: locks > Versions: 1.0 > Environment: Win XP, Sun JDK 1.5.0 > Reporter: Walter Raboch > Assignee: Dominique Pfister > Fix For: 1.0 > Attachments: SharedItemStateManager.diff > > JackRabbit is still hanging on the Node.lock() or Node.unlock() function. > ... everything fine until here... > s13: 4 > s13: 5 > s13: 6 > s13: 7 -> unlock() > s14: started. > s14: 1 -> session.getRootNode() > s15: started. > s15: 1 > s16: started. > I just find this failure during the first run (emtpy repository home directory). 2nd and 3th run are fine after killing the vm from first run, but with already initialized repository directory these time. > 1. rm -rf repository.home > 2. run -> hang > 3. kill > 4. run -> ok > 5. run -> ok -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira