Description
getRabbitmqConnection calls setCredentials without passing virtualHost, even though RABBIT.VIRTUAL_HOST is already read from the environment. As a result, the connection always lands on the default vhost (/) instead of the one configured via RABBIT_VIRTUAL_HOST.
This fails silently: if the default vhost happens to have an exchange with the same name as the intended one, publish succeeds with no error, but the message is unroutable there and RabbitMQ drops it — the message never reaches the queue on the correct vhost.
What type of PR contains?
Description
getRabbitmqConnectioncallssetCredentialswithout passingvirtualHost, even thoughRABBIT.VIRTUAL_HOSTis already read from the environment. As a result, the connection always lands on the default vhost (/) instead of the one configured viaRABBIT_VIRTUAL_HOST.This fails silently: if the default vhost happens to have an exchange with the same name as the intended one,
publishsucceeds with no error, but the message is unroutable there and RabbitMQ drops it — the message never reaches the queue on the correct vhost.What type of PR contains?