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

Posted to dev@jackrabbit.apache.org by "Alex Parvulescu (Commented) (JIRA)" <ji...@apache.org> on 2012/03/23 14:27:26 UTC

[jira] [Commented] (JCR-3227) VolatileIndex not closed properly

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

Alex Parvulescu commented on JCR-3227:
--------------------------------------

ported to 2.4 in rev 1304334.
                
> VolatileIndex not closed properly
> ---------------------------------
>
>                 Key: JCR-3227
>                 URL: https://issues.apache.org/jira/browse/JCR-3227
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.4
>            Reporter: Jukka Zitting
>            Priority: Minor
>             Fix For: 2.4.1, 2.6
>
>         Attachments: JCR-3227.patch
>
>
> The MultiIndex.resetVolatileIndex() method doesn't properly close the existing VolatileIndex instance before creating a new one. This can confuse the DynamicPooledExecutor reference count added in JCR-2836, leading to a background thread leak.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira