Error: “Mandatory property jcr:data cannot be removed” while publishing assets
The replication agent’s transport URI - (Uniform Resource Identifier) has an extra & (Sending a POST request to https://publish2useast1.stage.loyaltyone.adobecqms.net/bin/receive?sling:authRequestLogin=1&binaryless=true).
Description description
Environment
Adobe Experience Manager (AEM)
Issue
Replication queues are suddenly getting blocked when assets are published.
While messages [ 1] were present in the publisher instance logs, the author logs had the statement, Mandatory property jcr:data can not be removed, as part of replication exceptions [ 2] :
[ 1] *INFO* [ xxxxx] POST /bin/receive HTTP/1.1] com.day.cq.replication.impl.content.durbo.DurboImportTransformer Unable to set (protected) property ‘/content/dam/asset_folder/asset.jpg/jcr:content/renditions/original/jcr:content/binary_reference_jcr__data’ : javax.jcr.nodetype.ConstraintViolationException: No matching property definition: binary_reference_jcr__data = a1cbdabd2d4114766b63098a6e0f709cf9dad9861a2660f4bee7eb0f04560730:69185c7dd58c0fcc0724072b4e418146cd54d285:71150
[ 2] *ERROR* [ sling-threadpool-80b24cfc-26d8-479d-940f-1484c9ba9347-(apache-sling-job-thread-pool)-34-com_day_cq_replication_job_publish1useast1(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish < < error: com.day.cq.replication.ReplicationException: Repository error during node import: OakConstraint0022: /content/dam/asset_folder/asset.jpg/jcr:content/renditions/cq5dam.web.1280.1280.jpeg/jcr:content[ [ nt:resource] ] : Mandatory property jcr:data can not be removed
Resolution resolution
The replication agent’s transport URI - (Uniform Resource Identifier) has an extra & (Sending a POST request to https://publish2useast1.stage.loyaltyone.adobecqms.net/bin/receive?sling:authRequestLogin=1&binaryless=true).
The Transport URI was modified as part of the Certification renewal process for the Amazon Managed Services (AMS)-hosted Author and Publisher instances, which is when the URI encoding took place.
This encoding was producing errors for the author and publisher by mucking with the binary less replication.