jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2426) Deadlock in lucene (Jackrabbit 1.4.4)
Date Fri, 24 Sep 2010 15:13:33 GMT

     [ https://issues.apache.org/jira/browse/JCR-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-2426:
-------------------------------

    Priority: Minor  (was: Blocker)

Reducing priority as this doesn't seem to affect more recent Jackrabbit versions. I'd resolve
this as Won't Fix unless someone comes up with a repeatable test case and a patch for fixing
this. The recommended solution is to upgrade your deployment.

The 1.6.0 deadlock you noticed was fixed in JCR-2525.

> 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: Minor
>         Attachments: deadlock_2nd_setup.txt, deadlock_jackrabbit1.6.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