Gettig OakState0001: Unresolved conflicts error on asset import | Community
Skip to main content
asn_india
asn_india
Level 2
January 29, 2021
Solved

Gettig OakState0001: Unresolved conflicts error on asset import

  • January 29, 2021
  • 1 reply
  • 6190 views

Hi All,

We have a scheduled task that triggers a workflow which brings/imports assets from a ftp server/site. these assets are of type .psd (with average file size 35-40 MB).

We are observing lot of errors of type OakState0001 in log files, the asset count is fine...I mean all the assets are getting downloaded from ftp site and uploaded into AEM.

But there are quite a few errors in logs....and this causes lot of workflow failures in workflow console.

Apparently, there is some conflict arising with (DAM-Update-asset) workflow and workflow process that brings these assets from FTP site.

We enabled ConflictValidator logs and could see something like below --

org.apache.jackrabbit.oak.plugins.commit.ConflictValidator Commit failed due to unresolved conflicts in /content/dam/projects/company/january/012120_set_e/retouched/21PSDW_INSERT.jpg/jcr:content = {addExistingProperty = {jcr:lastModifiedBy = {workflow-p...,customer-asset-...}}}

 

org.apache.jackrabbit.oak.plugins.commit.ConflictValidator Commit failed due to unresolved conflicts in /content/dam/projects/company/january/012120_set_e/retouched/08IRENNA_1.psd/jcr:content/renditions/cq5dam.thumbnail.48.48.png/jcr:content = {addExistingProperty = {jcr:data = {<BINARY>,<BINARY>}}}

out of which "customer-asset-..." is our system user that is used to acquire resource resolver in workflow process that downloads and creates these assets in dam.

 

The code for workflow that imports assets gets resource resolver in below manner --

 

Map<String,Object> paramMap = new HashMap<>();
paramMap.put(ResourceResolverFactory.SUBSERVICE,"dam-asset-move");
try {
resourceResolver = resourceResolverFactory.getServiceResourceResolver(paramMap);

//

some code to connect to ftp site and loop for every asset

//

assetManager.createAsset(assetName,inputStream,mimeType,true);

 

The whole process of downloading assets from ftp site takes close to 2 hours ....since there are ~600 assets every day.

 

@joerghoh  any insights from you to investigate this further would help a lot!

Best answer by joerghoh

Hi,

This exception typically means that 2 sessions are working concurrently on the same node. Because of the MVCC pattern they don't get the updates the other session is performing on the node, and thus it fails on commit. One seems to be your process, while the other one being the AssetUpdate workflow.

 

AssetManager.createAsset(String path, InputStream is,String mimetype, boolean doSave)

 

seems to be the right now thing; even with "doSave = true" it will create the asset within a single commit. Also this commit seems to happen correctly, otherwise the workflow wouldn't start (there wouldn't be any asset to start on). So there must a 3rd session around, which tries to modify content. Can you paste the *full log messages* with these errors? Especially the name of the logger and the threadname is of interest.

 

(Technically it would be possible, that the asset you want to create is already there and that a workflow is currently running on it, while you do the call above. Can you rule that out?)

1 reply

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
January 30, 2021

Hi,

This exception typically means that 2 sessions are working concurrently on the same node. Because of the MVCC pattern they don't get the updates the other session is performing on the node, and thus it fails on commit. One seems to be your process, while the other one being the AssetUpdate workflow.

 

AssetManager.createAsset(String path, InputStream is,String mimetype, boolean doSave)

 

seems to be the right now thing; even with "doSave = true" it will create the asset within a single commit. Also this commit seems to happen correctly, otherwise the workflow wouldn't start (there wouldn't be any asset to start on). So there must a 3rd session around, which tries to modify content. Can you paste the *full log messages* with these errors? Especially the name of the logger and the threadname is of interest.

 

(Technically it would be possible, that the asset you want to create is already there and that a workflow is currently running on it, while you do the call above. Can you rule that out?)

    asn_india
    asn_indiaAuthor
    Level 2
    February 8, 2021

    Hi @joerghoh,

     

    Thank you so much for direction - It took me some time to investigate but yeah there were two workflows, one OOTB DAM Update asset and another one which is nothing but copy of DAM update asset extended with some custom steps at the end. Both these workflows were running on that folder.

    So I excluded this folder from OOTB DAM Update asset launcher and did not see Oakstate error in latest run.

    Thanks a ton again for your help!!

      Terms & ConditionsAccessibility statement

      Loading footer...