-
Notifications
You must be signed in to change notification settings - Fork 3
Description
Trying to migrate from ActiveMQ to RabbitMQ (clustered). In the RabbitMQ cluster you have to tie queues to a particular vhost. But in the cluster I have dns names rabbitmq1/2/3. I could create a single DNS entry to cover all 3 but then I'd lose resiliency as I'd only have 1 active connection and I'd rely on dns/connection failures to migrate me to an active node. So I'd rather have ongoing connections to all 3 different servers using the same vhost name so that if one fails stompman will automatically fail over to another connection.
I'd suggest the simplest way might be to add an optional vhost
argument to https://github.com/community-of-python/stompman/blob/main/packages/stompman/stompman/config.py#L29 defaulting to None
which would mean 'the same as host
' and hence preserve the back-compatibility.