A VMware snapshot is a copy of the virtual machine's disk file (VMDK) at a given point in time. Snapshots provide a change log for the virtual disk and are used to restore a VM to a particular point in time when a failure or system error occurs.
It seems the root reason cause the socket exception. So any solution in configuration to avoid socket exception in SWIFTMQ?
How did you force this split brain on your local PC? Probably by terminating the network connection of the replication channel with SwiftMQ Explorer or CLI. So this causes of course a socket exception. Another reason could be a network problem.
Any solution for those momentary VM suspend or network down when the period is less than heartbeat threshold 10 times * 2 seconds. Any configuration to re establish the connection rather than deactivate channel.
Well, NOW I understand the problem. If you are running them on a VM and suspend it for a while, the other instance goes into standalone. If you resume the VM, you have a split brain.
What you need to do is to shutdown the HA instance before you suspend and start it after the resume. Do it with a cron job or a script that you can run from a VM hook before / after these events occur.