[JCR-3483] Result set iterator causes infinite loop when used after session has been closed

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.2.13, 2.4.3, 2.5.2
• Fix Version/s: 0.9, 2.4.4, 2.5.3
• Assignee: Unico Hommes
• Reporter: Unico Hommes
• Created: 13/Dec/12 19:53
• Updated: 26/Aug/19 08:47
• Resolved: 13/Dec/12 20:09

Description

org.apache.jackrabbit.core.query.lucene.NodeIteratorImpl#fetchNext has a bug where it causes the iterator never to move on to the next element (node).

When the iterator is used after the session has been logged out the FetchNext#perform operation is never called because SessionState#perform throws an exception when first checking if the session is alive. This causes the current iterator node never to be reset.