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] Created: (JCR-2746) Deadlock caused by ObservationDispatcher
Date Tue, 14 Sep 2010 09:31:34 GMT
Deadlock caused by ObservationDispatcher 
-----------------------------------------

                 Key: JCR-2746
                 URL: https://issues.apache.org/jira/browse/JCR-2746
             Project: Jackrabbit Content Repository
          Issue Type: Bug
          Components: jackrabbit-core, observation
    Affects Versions: 2.1.1, 2.1.0, 2.0.0
            Reporter: Jukka Zitting
             Fix For: 2.2.0


The rate-limitation code we added in JCR-2402 to prevent the observation queue from growing
too large was a good idea, but the current implementation is a bit troublesome since it blocks
the thread while it still holds the journal lock, the SISM reader lock, and the SessionState
lock. This can cause a deadlock under heavy workloads if any of the observation listeners
attempts to reuse the session (not recommended/supported, but can still happen) or write to
the repository (quite likely).

To solve this problem we should move the rate-limiter code to outside the scope of any internal
locks.

-- 
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