Freigeben über

Service Bus client 3.2.2 is now live

  • Artikel

Check out our newest release for the Service Bus client library! This release was primarily focused on Event Hubs, but there are still a couple of fixes in there for Messaging and Relay customers.

The NuGet package can be found at https://www.nuget.org/packages/WindowsAzure.ServiceBus/3.2.2.

Below are the release notes:

  • EventHub/Messaging: Improve information in exception tracking in NamespaceManager to show namespace information in system tracker.
  • EventHub: Refresh Amqp redirection feature to work with new environment.
  • EventHub: Improve performance when using PrefetchSizeInBytes by not assuming worst case message size. Note that with this change it is now possible to exceed the cache size specified by the PrefetchSizeInBytes value (even though it is unlikly since we stop the credit at about 90%).
  • EventHub/Messaging: Fix a bug where in Amqp transport the client is passing the wrong audience when the token provider's scope is a namespace.
  • EventHub/Messaging: Improve information in exception tracking in NamespaceManager to show namespace information in system tracker.
  • EventHub: Improve EventData(byte[]) to avoid unnecessary memory allocation, and added new constructor that can take in ArraySegement which also avoid memory allocation.
  • EventHub: Fix a bug where IoT redirection fails when connecting to new namespaces
  • Messaging: Fix a bug in all OnMessage pump api where a rare race condition can lead to ObjectDisposedException being thrown from the pump when processing callback takes too long.
  • Messaging: Fix a bug in MessageReceiver and BrokeredMessage where user were seeing wrong exception message when performing Abandon() call in a non-PeekLock mode.
  • Relay: Migrate relay client side traces to use dynamic EventSource support.
  • Relay: Fixed an issue in relay connection which can lead to timeouts or hangs when establishing rendezvous connection.
  • Relay: Fixed an issue in relay when using Websockets with NTLM in a proxy scenario, where the security context can have an output buffer that Relay did not forward to the proxy (which we should have forwarded).
  • General: Fixed a bug in the WebSocket implementation where the underlying connection is not recreated in some case when keep-alive signal is not sent.