jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Pfister (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (JCR-963) Failed to build path error in cluster environment
Date Fri, 31 Aug 2007 08:06:30 GMT

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

Dominique Pfister reassigned JCR-963:
-------------------------------------

    Assignee: Dominique Pfister

> Failed to build path error in cluster environment
> -------------------------------------------------
>
>                 Key: JCR-963
>                 URL: https://issues.apache.org/jira/browse/JCR-963
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: clustering
>    Affects Versions: 1.3
>            Reporter: Xiaohua Lu
>            Assignee: Dominique Pfister
>
> we have a 4 machine cluster setup based on Jackrabbit 1.3. We have noticed the following
error on one of the four nodes 
> javax.jcr.ItemNotFoundException: failed to build path of 22b7932e-d2c2-46b6-90ee-66acfa8f4bb4:
ef223e61-d6d3-49ec-8fb5-5e4668877d39 has no child entry for 22b7932e-d2c2-46b6-90ee-66acfa8f4bb4
>         at org.apache.jackrabbit.core.HierarchyManagerImpl.buildPath(HierarchyManagerImpl.java:308)
>         at org.apache.jackrabbit.core.CachingHierarchyManager.buildPath(CachingHierarchyManager.java:163)
>         at org.apache.jackrabbit.core.HierarchyManagerImpl.getPath(HierarchyManagerImpl.java:356)
>         at org.apache.jackrabbit.core.CachingHierarchyManager.getPath(CachingHierarchyManager.java:224)
>         at org.apache.jackrabbit.core.ItemImpl.getPrimaryPath(ItemImpl.java:295)
>         at org.apache.jackrabbit.core.ItemImpl.getPath(ItemImpl.java:1381)
>         at mycompany.repository.jackrabbit.cache.SystemCache.cacheItem(SystemCache.java:338)
>         at mycompany.repository.jackrabbit.cache.SystemCache.getItemPath(SystemCache.java:297)
>         at mycompany.repository.jackrabbit.cache.SystemCache.getItemPath(SystemCache.java:271)
>         at mycompany.repository.jackrabbit.cache.SystemCache.getPermission(SystemCache.java:135)
>         at mycompany.repository.jackrabbit.cache.AccessControlPermissionCacheImpl.getPermission(AccessControlPermissionCacheImpl.java:38)
>         at mycompany.repository.jackrabbit.AccessControlManager.isGranted(AccessControlManager.java:238)
>         at mycompany.repository.jackrabbit.AccessControlManager.isGrantedBySubject(AccessControlManager.java:223)
>         at mycompany.repository.jackrabbit.AccessControlManager.isGranted(AccessControlManager.java:139)
>         at org.apache.jackrabbit.core.query.lucene.LazyQueryResultImpl.getResults(LazyQueryResultImpl.java:270)
>         at org.apache.jackrabbit.core.query.lucene.LazyQueryResultImpl.<init>(LazyQueryResultImpl.java:166)
>         at org.apache.jackrabbit.core.query.lucene.QueryImpl.execute(QueryImpl.java:164)
>         at org.apache.jackrabbit.core.query.QueryImpl.execute(QueryImpl.java:139)
>         at net.maven.mcr.base.JCRSessionWrapper.executeQuery(JCRSessionWrapper.java:222)
>         at net.maven.mcr.service.ServiceImpl.executeNodeQuery(ServiceImpl.java:303)
> When we look up for nodes with the given uuid 22b7932e-d2c2-46b6-90ee-66acfa8f4bb4, it
doesn't exist in the repository, I am confused why this uuid is provided to our implementation
of access control manager and how we can fix it without cleanup the repository? 

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


Mime
View raw message