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

[girishb83316758]

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

[girishb83316758]

@Jörg_Hoh @kautuk_sahni  Any directions here..?

[Jörg_Hoh · Accepted solution]

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.

[girishb83316758]

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??

[Jörg_Hoh]

As mentioned, please contact Adobe support to check if this is a known issue (I would wonder, though).

commit failed due to unresolved conflicts in /var/workflow/instances/server1/workflow_22/data/metadata

This error happened because the metadata of this workflow steps are modify concurrently; that should not happen, as the a workflow is not executed twice in parallel. Can you please double-check the path (you probably did not a copy&paste), because it should contain the name of the workflow as well.

unresolved conflicts in /content/dam/event-store/workflow-list.json/jcr:content

This message comes from a conflict in the DAM. This could possibly be caused by parallel write operations; doing some guess work: Do you have a workflow model, which runs on distinct payloads, but in the end always updates this single JSON (file)? In this case it's very likely that this exception occurrs (you run this workflow  with 2 payloads and they try to write concurrently on this node/file).

And of course there are many more chances to get concurrent modifications. Failing workflow steps are retried (IIRC 3 times), so a single instance of this failure would not result in a failing workflow).

So please check if you see a pattern in the failing paths, and when it comes to workflows (guessing from the thread name and the name of the logger) if a retry helped.

[gpunee]

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

[Prithvi9]

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]

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