This issue happens because of the UNICAST Cluster Messaging order.
To resolve this issue, set the message order enabled property. The property, MessageOrderingEnabled, belongs to the ClusterMBean. This property forces Unicast messages to be processed in strict order. By default, this property is not enabled. To enable the property, add the following line to the <cluster> element in $DOMAIN_HOME/config/config.xml: