You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Christan Keller (Created) (JIRA)" <ji...@apache.org> on 2012/02/09 10:46:59 UTC

[jira] [Created] (SLING-2408) JcrNodeResourceIterator logs on error level for deleted Nodes

JcrNodeResourceIterator logs on error level for deleted Nodes
-------------------------------------------------------------

                 Key: SLING-2408
                 URL: https://issues.apache.org/jira/browse/SLING-2408
             Project: Sling
          Issue Type: Improvement
    Affects Versions: JCR Resource 2.0.10
            Reporter: Christan Keller
            Priority: Minor


If you get a JcrNodeResourceIterator for examply via a ResourceResolver.resolve().
And you iterate over its entries. 
If it hapens that one of this entry is removed concurrently, the Ieterator gets an ItemNotFoundException and logs an Error.
The behavior is correct. Iterator goes on. The existant amount of Nodes is returned.

So I would set the log-level to warn, as this case is not an error.

Condtion:
---------------
Stirng path = /some/path
session.getNode(path).remove()

session.save();
resolverOtherSession.resolve(path)


Exception
---------------
2012 09:35:22.719 *ERROR* [pool-9-thread-3] 
org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResourceIterator seek: Problem creating Resource 
for next node, skipping javax.jcr.ItemNotFoundException: failed to build path of b126cb93-da9f-4306-
9033-9cdfd61514c0: 29a78b34-5009-4d36-be1a-240893c6f1a1 has no child entry for b126cb93-
da9f-4306-9033-9cdfd61514c0
	at org.apache.jackrabbit.core.HierarchyManagerImpl.buildPath(HierarchyManagerImpl.java:291)
	at 
org.apache.jackrabbit.core.CachingHierarchyManager.buildPath(CachingHierarchyManager.java:199)
	at org.apache.jackrabbit.core.HierarchyManagerImpl.getPath(HierarchyManagerImpl.java:395)
	at org.apache.jackrabbit.core.CachingHierarchyManager.getPath(CachingHierarchyManager.java:233)
	at org.apache.jackrabbit.core.ItemImpl.getPrimaryPath(ItemImpl.java:188)
	at org.apache.jackrabbit.core.NodeImpl.getPrimaryPath(NodeImpl.java:2753)
	at org.apache.jackrabbit.core.ItemImpl$2.perform(ItemImpl.java:379)
	at org.apache.jackrabbit.core.ItemImpl$2.perform(ItemImpl.java:376)
	at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
	at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
	at org.apache.jackrabbit.core.ItemImpl.getPath(ItemImpl.java:376)
	at org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.<init>(JcrNodeResource.java:88)
	at 
org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResourceIterator.seek(JcrNodeResourceIterator.jav


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (SLING-2408) JcrNodeResourceIterator logs on error level for deleted Nodes

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

Carsten Ziegeler resolved SLING-2408.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: JCR Resource 2.1.2

Thanks for reporting - fixed in trunk
                
> JcrNodeResourceIterator logs on error level for deleted Nodes
> -------------------------------------------------------------
>
>                 Key: SLING-2408
>                 URL: https://issues.apache.org/jira/browse/SLING-2408
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: JCR Resource 2.0.10
>            Reporter: Christan Keller
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: JCR Resource 2.1.2
>
>
> If you get a JcrNodeResourceIterator for examply via a ResourceResolver.resolve().
> And you iterate over its entries. 
> If it hapens that one of this entry is removed concurrently, the Ieterator gets an ItemNotFoundException and logs an Error.
> The behavior is correct. Iterator goes on. The existant amount of Nodes is returned.
> So I would set the log-level to warn, as this case is not an error.
> Condtion:
> ---------------
> Stirng path = /some/path
> session.getNode(path).remove()
> session.save();
> resolverOtherSession.resolve(path)
> Exception
> ---------------
> 2012 09:35:22.719 *ERROR* [pool-9-thread-3] 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResourceIterator seek: Problem creating Resource 
> for next node, skipping javax.jcr.ItemNotFoundException: failed to build path of b126cb93-da9f-4306-
> 9033-9cdfd61514c0: 29a78b34-5009-4d36-be1a-240893c6f1a1 has no child entry for b126cb93-
> da9f-4306-9033-9cdfd61514c0
> 	at org.apache.jackrabbit.core.HierarchyManagerImpl.buildPath(HierarchyManagerImpl.java:291)
> 	at 
> org.apache.jackrabbit.core.CachingHierarchyManager.buildPath(CachingHierarchyManager.java:199)
> 	at org.apache.jackrabbit.core.HierarchyManagerImpl.getPath(HierarchyManagerImpl.java:395)
> 	at org.apache.jackrabbit.core.CachingHierarchyManager.getPath(CachingHierarchyManager.java:233)
> 	at org.apache.jackrabbit.core.ItemImpl.getPrimaryPath(ItemImpl.java:188)
> 	at org.apache.jackrabbit.core.NodeImpl.getPrimaryPath(NodeImpl.java:2753)
> 	at org.apache.jackrabbit.core.ItemImpl$2.perform(ItemImpl.java:379)
> 	at org.apache.jackrabbit.core.ItemImpl$2.perform(ItemImpl.java:376)
> 	at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
> 	at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
> 	at org.apache.jackrabbit.core.ItemImpl.getPath(ItemImpl.java:376)
> 	at org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.<init>(JcrNodeResource.java:88)
> 	at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResourceIterator.seek(JcrNodeResourceIterator.jav

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Assigned] (SLING-2408) JcrNodeResourceIterator logs on error level for deleted Nodes

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

Carsten Ziegeler reassigned SLING-2408:
---------------------------------------

    Assignee: Carsten Ziegeler
    
> JcrNodeResourceIterator logs on error level for deleted Nodes
> -------------------------------------------------------------
>
>                 Key: SLING-2408
>                 URL: https://issues.apache.org/jira/browse/SLING-2408
>             Project: Sling
>          Issue Type: Improvement
>    Affects Versions: JCR Resource 2.0.10
>            Reporter: Christan Keller
>            Assignee: Carsten Ziegeler
>            Priority: Minor
>             Fix For: JCR Resource 2.1.2
>
>
> If you get a JcrNodeResourceIterator for examply via a ResourceResolver.resolve().
> And you iterate over its entries. 
> If it hapens that one of this entry is removed concurrently, the Ieterator gets an ItemNotFoundException and logs an Error.
> The behavior is correct. Iterator goes on. The existant amount of Nodes is returned.
> So I would set the log-level to warn, as this case is not an error.
> Condtion:
> ---------------
> Stirng path = /some/path
> session.getNode(path).remove()
> session.save();
> resolverOtherSession.resolve(path)
> Exception
> ---------------
> 2012 09:35:22.719 *ERROR* [pool-9-thread-3] 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResourceIterator seek: Problem creating Resource 
> for next node, skipping javax.jcr.ItemNotFoundException: failed to build path of b126cb93-da9f-4306-
> 9033-9cdfd61514c0: 29a78b34-5009-4d36-be1a-240893c6f1a1 has no child entry for b126cb93-
> da9f-4306-9033-9cdfd61514c0
> 	at org.apache.jackrabbit.core.HierarchyManagerImpl.buildPath(HierarchyManagerImpl.java:291)
> 	at 
> org.apache.jackrabbit.core.CachingHierarchyManager.buildPath(CachingHierarchyManager.java:199)
> 	at org.apache.jackrabbit.core.HierarchyManagerImpl.getPath(HierarchyManagerImpl.java:395)
> 	at org.apache.jackrabbit.core.CachingHierarchyManager.getPath(CachingHierarchyManager.java:233)
> 	at org.apache.jackrabbit.core.ItemImpl.getPrimaryPath(ItemImpl.java:188)
> 	at org.apache.jackrabbit.core.NodeImpl.getPrimaryPath(NodeImpl.java:2753)
> 	at org.apache.jackrabbit.core.ItemImpl$2.perform(ItemImpl.java:379)
> 	at org.apache.jackrabbit.core.ItemImpl$2.perform(ItemImpl.java:376)
> 	at org.apache.jackrabbit.core.session.SessionState.perform(SessionState.java:216)
> 	at org.apache.jackrabbit.core.ItemImpl.perform(ItemImpl.java:91)
> 	at org.apache.jackrabbit.core.ItemImpl.getPath(ItemImpl.java:376)
> 	at org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResource.<init>(JcrNodeResource.java:88)
> 	at 
> org.apache.sling.jcr.resource.internal.helper.jcr.JcrNodeResourceIterator.seek(JcrNodeResourceIterator.jav

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira