We are seeing spurious merge conflicts on publisher instances (AEM 6.1SP2) such as
merge-conflicts.log.2017-05-29:29.05.2017 09:20:09.437 *DEBUG* [172.18.27.44 [1496042409277] POST /bin/receive HTTP/1.1] org.apache.jackrabbit.oak.plugins.commit.ConflictValidator Commit failed due to unresolved conflicts in /content/dam/vrt/2017/02/23/wissper-r001-a0003-depot_WP00105034/jcr:content/vrt = {deleteChangedProperty = {cq:lastReplicated = {<N/A>,2017-05-29T09:20:09.093+02:00}}}
I suspect this is simply the replication agent trying to save some replicated asset as the stacktrace is showing
...
at com.sun.proxy.$Proxy11.save(Unknown Source)
at com.day.cq.replication.impl.content.durbo.DurboImporter.createNode(DurboImporter.java:295)
at com.day.cq.replication.impl.content.durbo.DurboImporter.createNode(DurboImporter.java:215)
at com.day.cq.replication.impl.ReplicationReceiverImpl.receive(ReplicationReceiverImpl.java:160)
at com.day.cq.replication.impl.servlets.ReplicationServlet.doPost(ReplicationServlet.java:206)
I do not understand where the merge conflict is coming from. I am quite sure we do not have code that deletes the cq:lastReplicated property.
Does the replication agent use multiple threads and sessions to handle replicated items? Or any other theories as to what is causing this merge conflict?