Contact Free trial Login

Microsoft Service Bus Connector Release Notes - Mule 4

Support Category: Select

Anypoint Connector for Microsoft Service Bus provides support for Microsoft Windows Service Bus (on-premises).

To implement message integration scenarios with Microsoft Azure, use the Microsoft Azure Service Bus Connector.

2.2.1

September 2, 2020

Compatibility

Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+

Fixed Issues

Fixed a Null Pointer Exception that occurred when using the Raise error component with the Message listener in a flow. (SE-17315)

Known Issues

  • The JMS selector that previously filtered incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus.

  • The maxConnections parameter is deprecated.

2.2.0

July 27, 2020

Compatibility

Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+

Fixed Issues

Fixed reported security vulnerabilities. (CONN-6252,CONN-6253,CONN-6254)

Known Issues

  • The JMS selector that previously filtered incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus.

  • The maxConnections parameter is deprecated

2.1.15

May 29, 2020

Compatibility

Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+

2.1.14

May 8, 2020

Compatibility

Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+

Fixed Issues

  • An exception occurred when disposing an object. (SE-15278).

Known Issues

  • The JMS selector used to filter incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus.

2.1.13

April 21, 2020

Compatibility

Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+

Fixed Issues

Fixed security vulnerabilities. (CONN-5680)

Known Issues

  • The JMS selector used to filter incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus.

2.1.12

March 9, 2020

Compatibility

Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+

Fixed Issues

Mule 4.2.2 on-premises did not clear out metaspace when redeploying an application. (SE-14929)

Known Issues

  • The JMS selector used to filter incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus.

2.1.11

February 28, 2020

Compatibility

Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+

Fixed Issues

The exposed SharedAccessSignatureProvider interface was fixed to allow the implementation of a SAS Token Provider. (SE-14685)

Known Issues

  • The JMS selector used to filter incoming messages is not supported by Microsoft Windows Service Bus Connector because it is not supported by Windows Service Bus.

2.1.10

January 20, 2020

Compatibility

Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+

Fixed Issues

  • Fixed the isssue in which a reconnection error occurred after producer inactivity. (SE-14544)

2.1.9

January 9, 2020

Compatibility

Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+

Fixed Issues

  • Consumer error after redeploying an app is now fixed. (SE-14336)

2.1.8

December 10, 2019

Compatibility

Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+

Fixed Issues

  • Fixed the unauthorized user error when using a SAS connection issue. (SE-14174)

2.1.7

November 11, 2019

Compatibility

Software Version

Mule

4.1.1 and later

Service Bus

Microsoft Windows Service Bus 1.1+

Fixed Issues

  • Fixed reconnection errors in a message producer. Previously, when using a cached producer, if a ConnectionException occurred, the connector tried to reconnect with the same state instead of re-establishing the connection. (CONN-4032)

2.1.6

November 5, 2019

Compatibility

Software Version

Mule

4.1.1 and later

Fixed Issues

  • Added specific error types for JMS exceptions. The connector now throws SERVICEBUS:PUBLISHING, SERVICEBUS:ILLEGAL_BODY, SERVICEBUS:DESTINATION_NOT_FOUND, or SERVICEBUS:SECURITY, depending on the case. (SE-13674)

2.1.5

October 30, 2019

Compatibility

Software Version

Mule

4.1.1 and later

Fixed Issues

  • Improved connection exception handling. (SE-13581)

  • Added Queue Prefetch parameter in Advanced connection to limit the consumer buffer. (SE-13618)

2.1.4

October 16, 2019

Compatibility

Software Version

Mule

4.1.1 and later

Fixed Issues

  • Fixed a typo in a logged message.

2.1.3

October 16, 2019

Compatibility

Software Version

Mule

4.1.1 and later

Fixed Issues

  • Improved logging for send operations. (SE-13581)

2.1.2

August 29, 2019

Compatibility

Software Version

Mule

4.1.1 and later

Fixed Issues

  • Fixed delivery delay functionality for send operations. (SE-12892)

2.1.1

June 19, 2019

Compatibility

Software Version

Mule

4.1.1 and later

Features

  • JMS 2.0 shared subscription - Added support for having multiple consumers subscribe to a single topic. This functionality distributes the topic’s message load among all subscribers.

2.1.0

April 16, 2019

Compatibility

Software Version

Mule

4.1.1 and later

Features

  • Redelivery policy options (maximum redeliveries and outcome) were added to the connector’s configuration.

Fixed Issues

  • When dealing with manual ACK, if the flow failed with an error, the message could be reprocessed indefinitely. This is now fixed by the addition of the Redelivery Policy configuration.

Known Issues

  • Automatic completion of queue/topic names, subscriptions and rules may not work in Design Center.

  • Under some scenarios, users can get an InterruptedException error on the Mule app startup. This does not affect the proper operation. To get rid of this message, check the Skip Connectivity Test checkbox in the connector’s configuration.

2.0.3

February 22, 2019

Compatibility

Software Version

Mule

4.1.1 and later

Fixed Issues

  • Connection leaks were fixed.

  • The connector would stop receiving messages when the flow threw an error. This was fixed.

Known Issues

  • Automatic completion of queue and topic names, subscriptions, and rules may not work in Design Center.

2.0.2

December 5, 2018

Compatibility

Software Version

Mule

4.1.1 and later

Fixed Issues

  • Previously, the connector leaked connections while publishing a message to a topic using the default caching strategy. The connector uses one or two JMS connections based on the configuration.

Known Issues

  • Automatic completion of queue or topic names, subscriptions, and rules may not work in Design Center.

  • In Design Center, the Live View feature does not work for most operations. In addition to this, the application log may be flooded with several Could not serialize object errors.

2.0.1

October 23, 2018

Compatibility

Software Version

Mule

4.1.1 and later

Fixed Issues

  • Manual ACK not working - Previously, when attempting to do a manual acknowledge of a message, the connector would lock the flow. This was now fixed, and doing this works as expected.

Known Issues

  • Automatic completion of queue and topic names, subscriptions and rules may not work in Design Center.

  • In Design Center, the Live View feature will not work for most operations. In addition to this, the application log may be flooded with several Could not serialize object errors.

  • The connector leaks connections while publishing a message to a topic using the default caching strategy. As a workaround, configure the connector to disable the caching strategy.

2.0.0

May 28, 2018

Compatibility

Software Version

Mule

4.1.1 and later

Features

  • Added support for Mule 4.

Known Issues

  • Automatic completion of queue and topic names, subscriptions, and rules may not work in Design Center.

  • In Design Center, the Live View feature does not work for most operations. In addition to this, the application log may be flooded with several Could not serialize object errors.

  • The connector leaks connections while publishing a message to a topic using the default caching strategy. As a workaround, configure the connector to disable the caching strategy.

Was this article helpful?

💙 Thanks for your feedback!