jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Petr Sochurek (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCR-3622) Deadlock when accessing to jackrabbit
Date Tue, 16 Jul 2013 14:24:49 GMT
Petr Sochurek created JCR-3622:
----------------------------------

             Summary: Deadlock when accessing to jackrabbit
                 Key: JCR-3622
                 URL: https://issues.apache.org/jira/browse/JCR-3622
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-core
    Affects Versions: 1.6
         Environment: RHEL, JBoss 5.1, Java 7
            Reporter: Petr Sochurek


Dear Appache Community,

We are using Jackrabbit 1.6.0 as a document store for our app running on JBoss5.1.

Since we started to use Jackrabbit more intensively, deadlocks in Jackrabbit internals occur.
Something inside is locked (for unknown reason) which lead to infinite blocking all threads
which want to use Jackrabbit.
On production environment the deadlock occurs every day and only JBoss restart helps.
Unfortunately I have no scenario to reproduce problem. 
The thread dump which shows dependencies between blocking threads is enclosed.    

I found similar bug solved in JCR-2554 but I am not sure whether relates to the same problem.
Could you please confirm that this is a JCR bug. And if so, is it repaired 1.6.5 version or
does exist any workaround?

Thank you very much,
PS

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message