Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Fri, 23 Mar 2012 13:27:26 +0000 (UTC)
From: "Alex Parvulescu (Updated) (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: 
 <2066990117.7824.1332509246755.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <704754035.2600.1328547599367.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (JCR-3227) VolatileIndex not closed properly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alex Parvulescu updated JCR-3227:
---------------------------------

    Fix Version/s: 2.6
    
> 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