When running a Mule application in single runtime instance mode, persistent queues work by serializing and storing the contents on the disk. However, when running the Mule application in cluster runtime instance mode, the persistent queues are backed up in the memory grid. Thereby, when a flow uses VM Connector to publish content to a queue, Mule runtime engine determines whether to process the message in the same origin node or to send the message to the cluster to pick another node. Using VM Connector facilitates the load distribution across a cluster.
In either single or cluster runtime instance mode, when using persistent queues, the data you send must be serializable. Although you can enable Kryo serialization to get a wider range of serializable values, Kryo does have some limitations. Refer to the considerations when using serialization documentation for details.
The problem here is it picks only the 1st mentioned Remarks (Correct) for both the duplicates.Result below when comparing with the master fileserial_numberRemarksSMC18290095CorrectSMC18290095correct 2b1af7f3a8