jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Unico Hommes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3483) Result set iterator causes infinite loop when used after session has been closed
Date Thu, 13 Dec 2012 20:06:13 GMT

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

Unico Hommes commented on JCR-3483:
-----------------------------------

Fix committed to trunk in revision 1421472.
                
> Result set iterator causes infinite loop when used after session has been closed
> --------------------------------------------------------------------------------
>
>                 Key: JCR-3483
>                 URL: https://issues.apache.org/jira/browse/JCR-3483
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>    Affects Versions: 2.2.13, 2.4.3, 2.5.2
>            Reporter: Unico Hommes
>            Assignee: Unico Hommes
>            Priority: Critical
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message