AEM workflow "Go-to" step executes twice in AEM 6.5 SP 12 | Community
Skip to main content
G
girishb83316758
Level 3
August 21, 2022
Solved

AEM workflow "Go-to" step executes twice in AEM 6.5 SP 12

  • August 21, 2022
  • 3 replies
  • 1754 views

Hi All,

 

we have a custom workflow in which the Go-TO step gets executed twice. which should not be happening. And this has started appearing after we upgraded our AEM 5.6.10 to AEM6.5.12.

 

We are seeing the below errors in the logs-

org.apache.jackrabbit.oak.plugins.commit.conflictvalidator commit failed due to unresolved conflicts in va4/workflow/instacnes/server1/workflow_22/data/metadata = {addExistingProperty = {cq:waitingToAdvance = {true,false}}}

 

 

org.apache.jackrabbit.oak.api.commitFailedException: oakstate0001: unresolved conflicts in va/workflow/instacnes/server1/workflow_22/data/metadata

 

job handler: [va4/workflow/instacnes/server1/update_asset/:/content/dam/event-store/workflow-list.json/jcr:content/renditions/original] org.apache.jackrabbit.oak.plugins.commit.conflictvalidator commit failed due to unresolved conflicts in /content/dam/event-store/workflow-list.json/jcr:content = {changeChangedProperty= {dam:assetState= {processed,unprocessed}}}

 

org.apache.jackrabbit.oak.api.commitFailedException: oakstate0001: unresolved conflicts in /content/dam/event-store/workflow-list.json/jcr:content

 

Could anyone let us know how this can be avoided.

 

 

Thanks

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 joerghoh

This message could originate from a race condition where 2 concurrent threads are trying to modify a node.

 

Please raise a ticket with Adobe support, if this behavior appeared with Sp12.

3 replies

G
girishb83316758Author
Level 3
August 22, 2022

@joerghoh @kautuk_sahni  Any directions here..?

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
August 22, 2022

This message could originate from a race condition where 2 concurrent threads are trying to modify a node.

 

Please raise a ticket with Adobe support, if this behavior appeared with Sp12.

    G
    girishb83316758Author
    Level 3
    August 23, 2022

    How should we resolve this concurrent threads/session issue?

     Are there any reference links? How to find which sessions are running concurrently in aem?

    Is there any hot fix package to install? Any thing like that??

      P
      Prithvi9
      March 7, 2023

      Hi girish - were you able to resolve this issue?

       

      We are facing same issue where GOTO step configured in workflow causes "org.apache.jackrabbit.oak.plugins.commit.conflictvalidator commit failed due to unresolved conflicts"

       

      If I update the ecma script(executed with GOTO step) returns true, we see this in error logs. Otherwise it works fine. The impact of this is: Ourr workflow is failed for first time and retried for 9 more times. The failure is also seen in the Inbox. 

       

      TIA

      Puneet


      Hi gpunee,

      We are also facing the same issue with the Goto Step, 

       

      Could you please share what was the work around for this issue because of this workflow fails and runs again...

       

       

      ManviSharma
      Adobe Employee
      ManviSharmaAdobe Employee
      Adobe Employee
      August 23, 2022

      Hi,

       

      The issue seems to be with your custom workflows. -->The error “: \org.apache.jackrabbit.oak.api.commitFailedException: oakstate0001: unresolved conflicts in va/workflow/instacnes/server1/workflow_22/data/metadata” is usually observed when there are a lot of instances running and they are stuck, the processing of workflows gets impacted. The reason for the workflow instances being stuck could be many like bulk activity or some overlap as shown in the error.

       

      Regards,

      Manvi Sharma

        Terms & ConditionsAccessibility statement

        Loading footer...