You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2008/03/20 10:25:24 UTC

[jira] Created: (JCR-1491) UUID check in BundleFsPersistenceManager.getListRecursive() leads to endless loop

UUID check in BundleFsPersistenceManager.getListRecursive() leads to endless loop
---------------------------------------------------------------------------------

                 Key: JCR-1491
                 URL: https://issues.apache.org/jira/browse/JCR-1491
             Project: Jackrabbit
          Issue Type: Bug
    Affects Versions: core 1.4.1, 1.4
            Reporter: Marcel Reutegger
            Priority: Minor
             Fix For: core 1.4.2


The UUID comparison in getListRecursive() is wrong and leads to an endless loop when the test PersistenceManagerIteratorTest.getAllNodeIds() is run on a workspace using BundleFsPersistenceManager.

I'm not sure this always happens, but for sure in a workspace with no content (just root and jcr:system nodes).

There's also an problem with the test case. In batch mode the after NodeId is set to the last id returned by the previous get all nodes fetch. This means batch retrieval is never actually tested, because there is no NodeId after the last one.

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


[jira] Updated: (JCR-1491) UUID check in BundleFsPersistenceManager.getListRecursive() leads to endless loop

Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger updated JCR-1491:
----------------------------------

          Component/s: jackrabbit-core
    Affects Version/s: core 1.4.2

> UUID check in BundleFsPersistenceManager.getListRecursive() leads to endless loop
> ---------------------------------------------------------------------------------
>
>                 Key: JCR-1491
>                 URL: https://issues.apache.org/jira/browse/JCR-1491
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.4, core 1.4.1, core 1.4.2
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.5
>
>
> The UUID comparison in getListRecursive() is wrong and leads to an endless loop when the test PersistenceManagerIteratorTest.getAllNodeIds() is run on a workspace using BundleFsPersistenceManager.
> I'm not sure this always happens, but for sure in a workspace with no content (just root and jcr:system nodes).
> There's also an problem with the test case. In batch mode the after NodeId is set to the last id returned by the previous get all nodes fetch. This means batch retrieval is never actually tested, because there is no NodeId after the last one.

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


[jira] Resolved: (JCR-1491) UUID check in BundleFsPersistenceManager.getListRecursive() leads to endless loop

Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved JCR-1491.
-----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: core 1.4.2)
                   1.5

Fixed in revision: 639221

> UUID check in BundleFsPersistenceManager.getListRecursive() leads to endless loop
> ---------------------------------------------------------------------------------
>
>                 Key: JCR-1491
>                 URL: https://issues.apache.org/jira/browse/JCR-1491
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.4, core 1.4.1, core 1.4.2
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.5
>
>
> The UUID comparison in getListRecursive() is wrong and leads to an endless loop when the test PersistenceManagerIteratorTest.getAllNodeIds() is run on a workspace using BundleFsPersistenceManager.
> I'm not sure this always happens, but for sure in a workspace with no content (just root and jcr:system nodes).
> There's also an problem with the test case. In batch mode the after NodeId is set to the last id returned by the previous get all nodes fetch. This means batch retrieval is never actually tested, because there is no NodeId after the last one.

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


[jira] Updated: (JCR-1491) UUID check in BundleFsPersistenceManager.getListRecursive() leads to endless loop

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-1491:
-------------------------------

    Fix Version/s:     (was: 1.5)
                   core 1.4.3

Merged to the 1.4 branch in revision 650341.

> UUID check in BundleFsPersistenceManager.getListRecursive() leads to endless loop
> ---------------------------------------------------------------------------------
>
>                 Key: JCR-1491
>                 URL: https://issues.apache.org/jira/browse/JCR-1491
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 1.4, core 1.4.1, core 1.4.2
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: core 1.4.3
>
>
> The UUID comparison in getListRecursive() is wrong and leads to an endless loop when the test PersistenceManagerIteratorTest.getAllNodeIds() is run on a workspace using BundleFsPersistenceManager.
> I'm not sure this always happens, but for sure in a workspace with no content (just root and jcr:system nodes).
> There's also an problem with the test case. In batch mode the after NodeId is set to the last id returned by the previous get all nodes fetch. This means batch retrieval is never actually tested, because there is no NodeId after the last one.

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