NServiceBus.Transport.AzureServiceBus 6.5.2 – Patch release available

Hi everyone,

We’ve just released NServiceBus.Transport.AzureServiceBus 6.5.2.

Improvements/Features

  • #1539 Allow subscribing without Manage rights when the subscription already exists
  • #1564 Retry subscription creation while the topic or forwarding destination isn’t visible yet

Fixed bugs

  • #1540 Warning is logged when publishing an event to a topic that does not exist yet
  • #1553 Publishing to a missing topic causes five-second delays and delays other new links

How to know if you are affected

You are affected by #1540 if you use version 6.3.0 or later with the topic-per-event topology, and your endpoints publish events before a subscriber has created their topics.

You are affected by #1553 if you use the topic-per-event topology, and your endpoints publish events to a topic that doesn’t yet exist.

Symptoms

For #1540, the transport logs a warning from NServiceBus.Transport.AzureServiceBus.MessageDispatcher for every publish to a topic that doesn’t exist. The publish itself doesn’t fail unless ThrowOnMissingTopicWhenPublishing is enabled.

For #1553, each publish to a topic that doesn’t exist takes about five seconds, and opening new links to other queues and topics on the same connection is delayed too.

When to upgrade

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

After upgrading, endpoints with installers enabled create a missing topic before they first publish to it, which uses the Manage rights that installers already require. Endpoints without installers log the warning once per topic after they start; to avoid the delay, create their topics in advance. With ThrowOnMissingTopicWhenPublishing enabled, the transport doesn’t create topics, and publishing to a missing topic still throws, now without logging a warning first.

Where to get it

You can install NServiceBus.Transport.AzureServiceBus 6.5.2 from NuGet.

Please read our release policy for more details.

With thanks,
The team in Particular