Hello Ashwini S.
Adding to the JMS suggestion: for the RabbitMQ Snaps, the Consumer’s Maximum connection attempts and Connection retry interval only retry the same connection. They don’t switch to a backup account.
he RabbitMQ account does have a Cluster Support option, which may let you list several nodes, but I haven’t confirmed the format. If Primary and Backup can be nodes of one cluster, quorum queues (Argument key x-queue-type, value quorum in the Consumer)would keep the queue available when a node goes down.
If they are two separate brokers, the Snap can’t fail over between them by itself, and you would need a load balancer or DNS alias in front of them, plus Shovel or Federation to sync messages. Filing an enhancement request is also worth doing.