You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Christopher Matthew Cavanaugh <ca...@gmail.com> on 2018/05/01 21:21:05 UTC

VLT-RCP between different AEM versions (6.0 and 6.3).

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.

Many thanks,

Matt

Re: VLT-RCP between different AEM versions (6.0 and 6.3).

Posted by Christopher Matthew Cavanaugh <ca...@gmail.com>.
Hi Julian,

Thank you for responding. I expect to follow up with more details soon, but
this provided me some initial assistance communicating with the vendor
performing the work.

The versions of the tool used were
3.1.16
3.1.44 (current version being used)

Many thanks,

Matt

On Wed, May 2, 2018 at 5:18 AM, Julian Reschke <ju...@gmx.de>
wrote:

> On 2018-05-02 07:11, Julian Reschke wrote:
>
>> ...
>>
>
> FWIW, I tried to improve logging and exception handling as part of <
> https://issues.apache.org/jira/browse/JCR-4292>.
>
> Best regards, Julian
>
>

Re: VLT-RCP between different AEM versions (6.0 and 6.3).

Posted by Christopher Matthew Cavanaugh <ca...@gmail.com>.
Hi Julian,

Thank you for responding. I expect to follow up with more details soon, but
this provided me some initial assistance communicating with the vendor
performing the work.

The versions of the tool used were
3.1.16
3.1.44 (current version being used)

Many thanks,

Matt

On Wed, May 2, 2018 at 5:18 AM, Julian Reschke <ju...@gmx.de>
wrote:

> On 2018-05-02 07:11, Julian Reschke wrote:
>
>> ...
>>
>
> FWIW, I tried to improve logging and exception handling as part of <
> https://issues.apache.org/jira/browse/JCR-4292>.
>
> Best regards, Julian
>
>

Re: VLT-RCP between different AEM versions (6.0 and 6.3).

Posted by Julian Reschke <ju...@gmx.de>.
On 2018-05-02 07:11, Julian Reschke wrote:
> ...

FWIW, I tried to improve logging and exception handling as part of 
<https://issues.apache.org/jira/browse/JCR-4292>.

Best regards, Julian

Re: VLT-RCP between different AEM versions (6.0 and 6.3).

Posted by Julian Reschke <ju...@gmx.de>.
On 2018-05-02 07:11, Julian Reschke wrote:
> ...

FWIW, I tried to improve logging and exception handling as part of 
<https://issues.apache.org/jira/browse/JCR-4292>.

Best regards, Julian

Re: VLT-RCP between different AEM versions (6.0 and 6.3).

Posted by Julian Reschke <ju...@gmx.de>.
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

Re: VLT-RCP between different AEM versions (6.0 and 6.3).

Posted by Julian Reschke <ju...@gmx.de>.
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