[JCR-3227] VolatileIndex not closed properly

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.4
• Fix Version/s: 2.4.1, 2.5
• Component/s: jackrabbit-core
• Assignee: Unassigned
• Reporter: Jukka Zitting
• Created: 06/Feb/12 16:59
• Updated: 27/May/12 09:51
• Resolved: 07/Feb/12 13:39

Description

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.