You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Claus Köll (JIRA)" <ji...@apache.org> on 2013/08/26 07:52:51 UTC

[jira] [Updated] (JCR-3655) Better Locking inside LockManagerImpl

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

Claus Köll updated JCR-3655:
----------------------------

    Description: 
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.

  was:
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 rather the current synchronized block.

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