jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Reschke <julian.resc...@gmx.de>
Subject Re: VLT-RCP between different AEM versions (6.0 and 6.3).
Date Wed, 02 May 2018 05:11:40 GMT
On 2018-05-01 23:21, Christopher Matthew Cavanaugh wrote:
> Hello all,
> 
> I have a client currently attempting to migrate from AEM 6.0 to AEM 6.3, 
> across the network, using VLT-RCP. Adobe has suggested a slightly older 
> version of VLT-RCP, expecting it to work. It seems to be working for  > most nodes,
except here:
> 
>     [ERROR] Internal error while retrieving
>     NodeInfo.java.io.IOException: '  ' 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:372)

>            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 o
> 
> 
> 
> They have not been able to identify the problematic nodes because of 
> their number and the lack of detail in the exception. Also, we are not 
> entirely certain the issue really relates to the whitespace chars above, 
> else I would expect other clients with many nodes to run into the same 
> exception.
> 
> Any hunches about what the likely issue is here? Is the tool resilient 
> enough to not expect character related issues? Or should we plan on 
> tweaking the VLT source code to make it work? I do not use VLT-RCP 
> regularly.

Very hard to say without more information.

- VLT version?
- does it happen upon reading from 6.0, or writing to 6.3?

Shouldn't it also be possible to do this in two steps, in order to find 
out what part is failing?

Best regards, Julian

Mime
View raw message