That file doesn't use "Hello" or "World" anywhere in it, and appears to
have only a single route within it. Can you help me to understand how it
lines up with the question you originally asked, where you have two
separate durable subscriptions, for Hello and World, where one is working
and the othe
Slow consumers can be identified for both queues and topics. But whereas
one of the primary responses (terminate the subscription and force the
consumer to re-subscribe) will protect the broker in the case of a
non-durable topic subscription (because the broker no longer needs to keep
those unconsu
You'd just specify the load balancer's hostname within the failover
transport's URI. When a connection is broken and a reconnect occurs, the
client will simply make a new connection request to the load balancer and
it will be the load balancer's responsibility to route the connection to
the current
