Proxy to JMS szenario - two different receiver queues in production

Hi guys,

I've got the following async scenario: Proxy to JMS.

Now I want to solve the following requirement:

In production environment are 2 instances (hosts) with the jms queues, one as a "normal" and one for reliability in case of any network errors, as fail over. In fact: we've got two different receiver queues (on different hosts with different ports) in case of a host is not available.

Is there a way to handle the second queue in receiver JMS-adapter?

I thought about "replyTo destination" in ASMA with Dynamic Configuration:

-> getting the hostname in Dynamic Configuration and see if we are on production instance (for test and development that doesn't matter)

-> make a lookup in Dynamic Configuration to check the availability ot the default host

-> in case of non-availability: overwrite the default host and default queue entry with the available host and available queue

-> in ASMA: host & queue-entry in "additional properties"

Any other suggestions are welcome 😊

If you have ideas far out from my thoughts feel free to tell 😊

Thanks a lot,

Stefan