Versioning error in logs | Community
Skip to main content
H
hardik11071994
October 5, 2020
Solved

Versioning error in logs

  • October 5, 2020
  • 2 replies
  • 2265 views

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

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by diksha_mishra

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-assets.html 

2 replies

diksha_mishra
Community Advisor
diksha_mishraCommunity AdvisorAccepted solution
Community Advisor
October 5, 2020

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-assets.html 

    vanegi
    Adobe Employee
    vanegiAdobe Employee
    Adobe Employee
    October 13, 2020

    @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!!

      H
      Hardik-11071994
      October 15, 2020

       

      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

      Terms & ConditionsAccessibility statement

      Loading footer...