User Profile

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 mod...

Hi Vikas, any update on this?

Hi I have checked with adobe daycare team, they mentioned : They advise upgrade to AEM 6.5.5 since it has been already backported since AEM 6.5.4. But I have checked on 6.5.5 , we are still getting the issue. Any advise. ? I can see in console we are getting error at OOTB clientlib : (Line no 345 )/libs/dam/gui/coral/components/admin/moveassetwizard/clientlibs.js

Hi Diksha, I did not get you can you please eblobarate? This issue we are getting when we try to move the published assets in bulk usually 6+ at a time from one folder to another , it keep spinning in move wizard and we can see 500 internal server error in console. We are using AEM 6.5.5

Hi Vikas,Hope you are well! We can see below error in logs, is this something which cause this issue?(dam/scene7/asset/activation)] com.day.cq.dam.scene7.impl.listener.Scene7ActivationJobConsumer Repository exception during Scene7 asset activation We already proposed the service pack upgrade, however, when we check with adobe scene7 team, they mentioned there were no sync between AEM and scene7 related fixes in service pack 6.5.6. Please advise. Thanks!

Hi Mate,Can you please tell me how you identify the multiple session and how did you fix this issue.?