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-3655) Better Locking inside LockManagerImpl
Date Mon, 07 Oct 2013 19:49:53 GMT

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

Jukka Zitting updated JCR-3655:
-------------------------------

    Fix Version/s:     (was: 2.6.3)
                   2.6.4

> Better Locking inside LockManagerImpl
> -------------------------------------
>
>                 Key: JCR-3655
>                 URL: https://issues.apache.org/jira/browse/JCR-3655
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.6.2, 2.7
>            Reporter: Claus Köll
>            Assignee: Claus Köll
>             Fix For: 2.6.4, 2.7.1
>
>         Attachments: JCR-3655.patch
>
>
> Its possible to get a Deadlock during the TimeoutHandler is running.
> As tried to fix that problem in JCR-3605 i found that the problem is hard to fix because
of locking the
> ItemStateManager during modifying the lock properties. It would be better to use a XAReentrantLock
than the current synchronized block.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message