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 (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/07 14:41:03 UTC

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

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

Alex Parvulescu resolved JCR-3227.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4.1

> The null assignment can be skipped since the next statement just overrides it.
agreed

fixed in rev: 1241461
                
> 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
>
>         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