Versioning error in logs

[#1]

Hi Team,

We are getting this error in logs, any advise to resolve this ?

javax.jcr.version.VersionException: OakVersion0001: Cannot change property jcr:lastModifiedBy on checked in node

Thanks

Hardik

[#2 · Accepted solution]

If this error pertains to a specific asset in DAM, can you please check if the asset is in "Checked in" status. This happens when one user locks their asset/image in order to restrict editing by other users in AEM.

You canverify this by following the steps here: https://docs.adobe.com/content/help/en/experience-manager-64/assets/managing/check-out-and-submit-as...

[Hardik-11071994]

@hardik11071994,

It looks like when this asset is being processed there is some concurrent write activity to the node. Hence the OakState0001 errors.

Also the resource where you see the problem is checked in and it is unable to offload. This seems to be causing the problem.

Please try to remove the check-in property by checking out.

Steps to checkout property:

1) Go to CRX Explorer

2) Navigate to the /jcr:content node for the affected image.

3) Click on the Versions button on the top menu bar, click on Checkout.

Thanks!!

[Hardik-11071994]

Hi @vanegi 

Below explanation is correct :

It looks like when this asset is being processed there is some concurrent write activity to the node. Hence the OakState0001 errors.

What is best practice to follow here? we observe that sometime session.save() unable to save and throw the conflict error. Sometimes last modified date xmp writeback not able to update because node might be checked in by other process.

We have custom steps in workflows and that require xmp writeback to run to update last modified date so how to avoid such conflict to occur?

please advise

Thanks

[hardik11071994]

Hi @vanegi 

xmp writeback is triggering while node modified as per launcher configuration and causing lots of conflict issues. 

Due to this conflict, our custom workflow/steps/jobs failing and many other issues. We really looking for right solution to fix this conflict issue.

Please let us know if any advise. thanks in advance.

[Hardik-11071994]

Hi @vanegi 

Any advise? 

We can see whenever we update any node xmp writeback is triggering and it's conflicting so how to avoid such issues?

How can we make sure xmp writeback run only when that asset checkout by the other process?