jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2426) Deadlock in lucene (Jackrabbit 1.4.4)
Date Wed, 09 Dec 2009 09:22:18 GMT

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

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

That looks very strange.

The JVM says:

"IndexMerger":
  waiting to lock monitor 0x03764818 (object 0x80c376b0, a org.apache.lucene.store.FSDirectory$FSIndexInput),
  which is held by "jmssecondaryApplnJobExecutor-7"

this is not correct. "jmssecondaryApplnJobExecutor-7" does not hold this lock.

This might be a JVM issue. What kind of JVM are you using? See also related reports here:
http://forums.sun.com/thread.jspa?messageID=2941439


> 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
>             Fix For: core 1.4.4
>
>         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