Hi everyone,
We’ve just released NServiceBus.MessagingBridge 5.1.1 and 4.0.6.
Fixed bugs
- #849 Bridge ignores custom queue address when forwarding messages to an endpoint
How to know if you are affected
You are affected if you register an endpoint on the bridge with a custom queue address, using new BridgeEndpoint(name, queueAddress) or BridgeTransport.HasEndpoint(name, queueAddress). A custom queue address is required, for example, for MSMQ endpoints and ServiceControl instances that run on a different machine than the bridge.
Symptoms
Messages that the bridge forwards to the endpoint are not sent to the custom queue address. Instead, they are sent to the queue named after the endpoint, which for MSMQ is a queue on the machine running the bridge. If that queue does not exist, the messages are moved to the bridge error queue (bridge.error by default). If it does exist, the messages are delivered to it and are never processed by the intended endpoint.
When to upgrade
You should upgrade immediately if you are affected. Otherwise, you should upgrade during your next maintenance window.
After upgrading, check the queue named after the endpoint on the machine running the bridge, and the bridge error queue. Messages that ended up there before the upgrade are not moved automatically. Move them with QueueExplorer or PowerShell scripts.
Where to get it
You can install the new versions of NServiceBus.MessagingBridge from NuGet.
Please read our release policy for more details.
With thanks,
The team in Particular