[jira] [Commented] (JCR-3399) Shared ISM does not release the internal Writelock if something unexpectedly is happening in externalUpdate

["Unico Hommes (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCR-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13464591#comment-13464591 ] 

Unico Hommes commented on JCR-3399:
-----------------------------------

Backported to the 2.2 branch in revision 1390916.
                
> Shared ISM does not release the internal Writelock if something unexpectedly is happening in externalUpdate
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: JCR-3399
>                 URL: https://issues.apache.org/jira/browse/JCR-3399
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.4.2
>            Reporter: Claus Köll
>            Assignee: Claus Köll
>             Fix For: 2.2.13, 2.4.3, 2.5.1
>
>         Attachments: JCR-3399.patch
>
>
> We have seen a deadlock if a OutOfMemoryError has occurred in externalUpdate inside the SISM.
> We should release the lock in finally 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