jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Martinez (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2426) Deadlock in lucene (Jackrabbit 1.4.4)
Date Sat, 13 Feb 2010 22:20:28 GMT

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

Antonio Martinez commented on JCR-2426:
---------------------------------------

When analyzing the threaddump with TDA we see:
    This thread dump contains monitors without a locking thread information. This means, the
monitor is hold by a system thread or some external resource.

The class involved "FSIndexInput" uses "Descriptor" class, which has overridden the finalize
method and eventually calls RandomAccessFile "close" and "finalize" methods.
Therefore the is possible that the holding thread is a system thead

> 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: Critical
>         Attachments: deadlock_summary.txt
>
>
> We get a deadlock in lucene part of jackrabbit (see deadlock_summary.txt)
> This issue has been observed in a production setup 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.


Mime
View raw message