Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1667788947.276641266233608169.JavaMail.jira@brutus.apache.org>
Date: Mon, 15 Feb 2010 11:33:28 +0000 (UTC)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-2426) Deadlock in lucene (Jackrabbit 1.4.4)
In-Reply-To: <1879342699.1260220819300.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JCR-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833769#action_12833769 ] 

Marcel Reutegger commented on JCR-2426:
---------------------------------------

> This issue has happened in another setup

can you please provide more details on that setup? JVM version, thread dumps, etc.

> Deadlock in lucene (Jackrabbit 1.4.4)
> -------------------------------------
>
>                 Key: JCR-2426
>                 URL: https://issues.apache.org/jira/browse/JCR-2426
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: indexing
>    Affects Versions: core 1.4.4
>            Reporter: Antonio Martinez
>            Priority: Blocker
>         Attachments: deadlock_summary.txt
>
>
> We get a deadlock in lucene part of jackrabbit (see deadlock_summary.txt)
> This issue has been observed in two different production setups running Jackrabbit 1.4.4 in cluster configuration

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.