You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2009/04/20 19:06:47 UTC

[jira] Resolved: (JCR-1886) jcr2spi: Unprocessed ItemInfos call to RepositoryService#getItemInfos

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

Michael Dürig resolved JCR-1886.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.5

Fixed at revision 766756  


> jcr2spi: Unprocessed ItemInfos call to RepositoryService#getItemInfos
> ---------------------------------------------------------------------
>
>                 Key: JCR-1886
>                 URL: https://issues.apache.org/jira/browse/JCR-1886
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr2spi
>    Affects Versions: 1.5.0
>            Reporter: angela
>            Assignee: Michael Dürig
>             Fix For: 1.5.5, 1.6.0
>
>
> stefan reported the following problem:
> - batchread config reads with depths infinity
> - invalidate tree by calling Node.refresh(false)
> - force loading of the tree (e.g. Node.getPath())
> afterwards, there may still be invalidated item states indicating that not all ItemInfos were processed.
> consequently, there are additional calls to getItemInfos that should have been covered by the loading of the tree.
> the problem occuring is not related to limitation of the item-cache size.
> problem analysis:
> there is a bug in WorkspaceItemStateFactory#createItemStates.
> there is a wrapper built around the ItemInfo-Iterator but later on the ItemInfo-Iterator is used instead of the wrapper, which pre-fetches items from the underlying iterator and process them upon hasNext()/next().

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.