Hi @vanegi Any advise? We can see whenever we update any node xmp
writeback is triggering and it's conflicting so how to avoid such
issues? How can we make sure xmp writeback run only when that asset
checkout by the other process?
Greetings @hamidk92094312 , Pain area :[1] There are not any audit
information on namespace.i.e. Who created and when? Is auto generated or
manually created...etc.So there are no ways to trace out how these
external namespace coming into the picture. [2] There is no way to find
all list of assets which contains particular namespace properties. i.e.
If I want to find all list of assets having namespace "ns7:" Issue is
because of these external metadata, these assets are coming into picture
while ...
Description - While uploading new assets from external system, those
assets might contains some metadata properties. While uploading it to
AEM, it's auto generating namespace and preserving those metadata. Which
we would like to prevent using this feature request if possible, Only
registered namespace metadata should preserve.Why is this feature
important to you - It's creating issues while doing full text search and
also impacting search speed. It certainly improve the system
performance.How wo...
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 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 teamWe are having AEM 6.5.5. Issue is when we are trying to do bulk
movement of asset it fails and give 500 internal server error in
console. please advise , what could be the issue? Thanks
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!
