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 Fri, 26 Feb 2010 23:08:05 GMT

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

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

Moving to a newer version of Java is too risky for customer now.

What I have done is to move to newer version of Jackrabbit 1.6.0 (and I also used NIOFS).
With this I'm getting a different deadlock - see deadlock_jackrabbit1.6.0.txt (again only
seen in performance setup after some time with high activity in the JCR)

> 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_2nd_setup.txt, 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.


Mime
View raw message