NServiceBus.MessagingBridge 3.1.0 – Minor release available

Announcements
,
1

Hi everyone,

We’ve just released NServiceBus.MessagingBridge 3.1.0.

Fixed bugs

  • #480 Bridge does not translate the ReplyToAddress for failed messages and retries
  • #505 MSMQ remote addresses can’t be configured

How to know if you are affected

You are affected by #480 if:

  • You have endpoints which reply to messages
  • You are using ServiceControl
  • You retry a failed message with an origin or destination endpoint that has moved to another side of the bridge

You are affected by #505 if you are using MSMQ and you need to configure a custom queue address with a specific server name specified, e.g. endpoint@servername, to enable the bridge to forward messages to a remote MSMQ server.

Symptoms

For #480, an error is thrown by the bridge when the message is retried.

For #505, an error is thrown by the bridge when it attempts to shovel the message.

When to upgrade

You should upgrade immediately if you are affected. Otherwise, you should upgrade during your next maintenance window.

For the bridge to translate ReplyTo headers for failed messages and retries, TranslateReplyToAddressForFailedMessages must be enabled.

Where to get it

You can install NServiceBus.MessagingBridge 3.1.0 from NuGet.

Please read our release policy for more details.

With thanks,
The team in Particular