Expand my Community achievements bar.

Renovator MCP tool Move Operation

Avatar

Level 3

We were using Renovator tool to perform MOVE operation in AEM Cloud Service Environment. We have observed One of the moves seemed to go through but it had one error. I tried another move and it wasn’t completed as it got 40% done. Any pointers like MCP accepts only one process at a time. We have started new process while other old process is still going on. It is not accepted? What is the expected behavior.

thanikon_0-1671690336274.png

 

Error Shown:

com.adobe.acs.commons.mcp.impl.processes.renovator.Renovator Fatal uncaught error in moveTree {}
com.adobe.acs.commons.mcp.impl.processes.renovator.MovingException: Error when moving node /content/dam/{image path}: OakState0002: Conflicting concurrent change on branch commits [r185354594ee-0-2]

 

Thanks,

5 Replies

Avatar

Employee

@thanikon The processes are queued , the previous process has to complete / throw an error before the next MCP process in queue is picked up and processed.

Avatar

Level 3

Thank you for the reply @digarg . I am observing few things when i am using this tool.

  1. Process is taking long time(more than 4 hours) and not getting completed. 
  2. Observed few sub folders got moved and few image paths are having issue. Throwing error and it is saying-   org.apache.sling.api.resource.PersistenceException: Unable to commit changes to session. at org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.commit(JcrResourceProvider.java:562) at org.apache.sling.resourceresolver.impl.providers.stateful.AuthenticatedResourceProvider.commit(AuthenticatedResourceProvider.java:240) at org.apache.sling.resourceresolver.impl.helper.ResourceResolverControl.commit(ResourceResolverControl.java:531) at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.commit(ResourceResolverImpl.java:1031) at com.adobe.acs.commons.fam.impl.ReusableResolver.commit(ReusableResolver.java:69) at com.adobe.acs.commons.fam.impl.ReusableResolver.free(ReusableResolver.java:60) at com.adobe.acs.commons.fam.impl.ActionManagerImpl.withResolver(ActionManagerImpl.java:205) at com.adobe.acs.commons.fam.impl.ActionManagerImpl.runActionAndLogErrors(ActionManagerImpl.java:167) at com.adobe.acs.commons.fam.impl.ActionManagerImpl.lambda$deferredWithResolver$0(ActionManagerImpl.java:159) at com.adobe.acs.commons.fam.impl.TimedRunnable.run(TimedRunnable.java:91) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: javax.jcr.InvalidItemStateException: OakState0002: Conflicting concurrent change on branch commits [r1857798bb81-0-3] at org.apache.jackrabbit.oak.api.CommitFailedException.asRepositoryException(CommitFailedException.java:238) at org.apache.jackrabbit.oak.api.CommitFailedException.asRepositoryException(CommitFailedException.java:213) at

Any suggestion/solution for this failure.

Thanks,

Avatar

Employee

@thanikon  : how many assets/size of assets you are trying to move ? Can you ensure that this activity is carried out in off peak hours when there is no possibility of concurrent operations on assets that you are wanting to move. Does it fail for assets under a workflow/review/editing state ?

Avatar

Level 3

We are trying to move a parent folder which has 4-5 child folders and there are sub child folders as well. Hierarchy we have is /content/dam/first parent/second parent/third parent/level1/level2/level3/level4/level5 and source we are giving is /content/dam/first parent/second parent/third parent. We are seeing error when it is moving images under level5 to the destination. In a total we have more than 4k assets under the source path we have provided.

Avatar

Community Advisor

@thanikon Have you tried moving level 5 to level 4 first and so on? Move is actually is a heavy operation and consumes alot of resources. 

Or was this issue resolved?