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

Thierry Ygé commented on JCRVLT-95:
-----------------------------------

It seems also that even if we had the jcrlog it cannot trace what is the root 
cause of the failure.

It would need changes most likely in the code that is seen in the stacktrace.

{code}
at 
org.apache.jackrabbit.spi2davex.ItemInfoJsonHandler.key(ItemInfoJSONHandler.java:205)
at org.apache.jackrabbit.commons.json.JsonParser.parse(JsonParser.java:108)
at org.apache.jackrabbit.commons.json.JsonParser.parse(JsonParser.java:73)
at 
org.apache.jackrabbit.spi2davex.RepositoryServiceImpl.getItemInfos(RepositoryServiceImpl.java:365)
at 
org.apache.jackrabbit.jcr2spi.state.WorkspaceItemStateFactory.createDeepNodeState(WorkspaceItemStateFactory.java:122)
at 
org.apache.jackrabbit.jcr2spi.state.TransientISFactory.createDeepNodeState(TransientISFactory.java:106)
at 
org.apache.jackrabbit.jcr2spi.hierarchy.NodeEntryImpl.loadNodeEntry(NodeEntryImpl.java:1163)
at 
org.apache.jackrabbit.jcr2spi.hierarchy.NodeEntryImpl.getDeepNodeEntry(NodeEntryImpl.java:429)
at 
org.apache.jackrabbit.jcr2spi.hierarchy.HierarchyManagerImpl.getNodeEntry(HierarchyManagerImpl.java:137)
at 
org.apache.jackrabbit.jcr2spi.ItemManagerImpl.getNode(ItemManagerImpl.java:168)
at org.apache.jackrabbit.jcr2spi.SessionImpl.getNode(SessionImpl.java:513)
{code}

In the case here apparently some hidden files added on the file system on which 
the generated package was created add some invalid characters in the name. 
"._Icon\r" for example. (it was found analyzing the .tidy.1.json request that 
is sent to the source).

It would have helped to find this faster if the tool would provide the real 
original source of the error.

> Add more detailled in the log about the path / source of an issue to better / 
> quickly remove blocker
> ----------------------------------------------------------------------------------------------------
>
>                 Key: JCRVLT-95
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-95
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: RCP
>    Affects Versions: 3.1.18
>            Reporter: Thierry Ygé
>
> In a recent use case, following stack trace could be seen on a failing RCP 
> task.
> 16.06.2015 09:12:04.424 *ERROR* [Vault RCP Task - 
> 9553e90f-8304-4a99-8c37-526e84ae2dea] 
> org.apache.jackrabbit.spi2davex.RepositoryServiceImpl Internal error while 
> retrieving NodeInf
> o.
> java.io.IOException: '^M' not allowed in name
> at 
> org.apache.jackrabbit.spi2davex.ItemInfoJsonHandler.key(ItemInfoJSONHandler.java:205)
> at org.apache.jackrabbit.commons.json.JsonParser.parse(JsonParser.java:108)
> at org.apache.jackrabbit.commons.json.JsonParser.parse(JsonParser.java:73)
> at 
> org.apache.jackrabbit.spi2davex.RepositoryServiceImpl.getItemInfos(RepositoryServiceImpl.java:365)
> at 
> org.apache.jackrabbit.jcr2spi.state.WorkspaceItemStateFactory.createNodeState(WorkspaceItemStateFactory.java:93)
> at 
> org.apache.jackrabbit.jcr2spi.state.TransientISFactory.createNodeState(TransientISFactory.java:97)
> at 
> org.apache.jackrabbit.jcr2spi.hierarchy.NodeEntryImpl.doResolve(NodeEntryImpl.java:990)
> at 
> org.apache.jackrabbit.jcr2spi.hierarchy.HierarchyEntryImpl.resolve(HierarchyEntryImpl.java:134)
> at 
> org.apache.jackrabbit.jcr2spi.hierarchy.HierarchyEntryImpl.getItemState(HierarchyEntryImpl.java:253)
> at 
> org.apache.jackrabbit.jcr2spi.hierarchy.NodeEntryImpl.getItemState(NodeEntryImpl.java:71)
> at 
> org.apache.jackrabbit.jcr2spi.hierarchy.NodeEntryImpl.getNodeState(NodeEntryImpl.java:363)
> at org.apache.jackrabbit.jcr2spi.state.ItemState.getParent(ItemState.java:213)
> at 
> org.apache.jackrabbit.jcr2spi.state.NodeState.retrieveDefinition(NodeState.java:465)
> at 
> org.apache.jackrabbit.jcr2spi.state.NodeState.getDefinition(NodeState.java:316)
> at org.apache.jackrabbit.jcr2spi.NodeImpl.getDefinition(NodeImpl.java:857)
> at 
> org.apache.jackrabbit.vault.util.RepositoryCopier.copy(RepositoryCopier.java:314)
> at 
> org.apache.jackrabbit.vault.util.RepositoryCopier.copy(RepositoryCopier.java:277)
> at org.apache.jackrabbit.vault.rcp.impl.RcpTask.run(RcpTask.java:200)
> at java.lang.Thread.run(Thread.java:745)
> It would have been good to have the information about the exact node path 
> where this issue occurred. Maybe some additional logging message could be 
> added to be more precise on which working item it failed.
> {quote}
>       We found the content tree that the offending content was in and removed 
> it from the server. Once it was removed we could once again migrate the 
> content from our production server.
> Would have been nice if the logging when in trace actually logged where it 
> was in processing the tree.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to