Flex Gateway新着情報
Governance新着情報
Monitoring API ManagerSupport 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.
May 2, 2024
The connector is now compatible with Java 17.
Software | Version |
---|---|
Mule |
4.3.0 and later |
Anypoint Studio |
7.1 and later |
OpenJDK |
8, 11, and 17 |
Microsoft Service Bus REST API |
v2 |
February 7, 2024
Software | Version |
---|---|
Mule |
4.3.0 and later |
Anypoint Studio |
7.1 and later |
Microsoft Service Bus REST API |
v2 |
The netty-codec-http2 dependency is upgraded to version 4.1.100.Final to address a reported security vulnerability. | W-14462879. |
---|
September 21, 2023
The Guava library is upgraded from com.google.guava : guava : 23.6.1-jre to com.google.guava : guava : 32.0.1-jre.
The Jackson Core library is upgraded from com.fasterxml.jackson.core:jackson-core:2.8.6 to com.fasterxml.jackson.core:jackson-core:2.15.2.
The Netty Codec component is upgraded from library io.netty: netty-codec:4.1.50.Final to io.netty: netty-codec:4.1.94.Final.
The Netty Handler component is upgraded from library io.netty: netty-handler:4.1.50.Final to io.netty: netty-handler:4.1.94.Final.
Software | Version |
---|---|
Mule |
4.3.0 and later |
Anypoint Studio |
7.1 and later |
Microsoft Service Bus REST API |
v2 |
Issue Resolution | ID |
---|---|
The Guava library is upgraded from com.google.guava : guava : 23.6.1-jre to com.google.guava : guava : 32.0.1-jre. |
W-13844872 |
The Jackson Core library is upgraded from com.fasterxml.jackson.core:jackson-core:2.8.6 to com.fasterxml.jackson.core:jackson-core:2.15.2. |
W-13844857 |
The Netty Codec component is upgraded from library io.netty: netty-codec:4.1.50.Final to io.netty: netty-codec:4.1.94.Final. |
W-13844837 |
The Netty Handler component is upgraded from library io.netty: netty-handler:4.1.50.Final to io.netty: netty-handler:4.1.94.Final. |
W-13844841, W-13844878. |
May 27, 2022
Software | Version |
---|---|
Mule |
4.1.1 and later |
Microsoft Azure Storage Client SDK |
5.0.0 |
Service Bus |
Microsoft Windows Service Bus 1.1+ |
Issue | ID |
---|---|
Fixed reported security vulnerabilities by upgrading the spring-beans package from |
W-11195302 |
April 21, 2022
Software | Version |
---|---|
Mule |
4.1.1 and later |
Service Bus |
Microsoft Windows Service Bus 1.1+ |
Issue | ID |
---|---|
Fixed reported security vulnerabilities by upgrading the spring-context package from |
W-10996432 |
April 16, 2019
Redelivery policy options (maximum redeliveries and outcome) were added to the connector’s configuration.
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.
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.
October 23, 2018
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.
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.
May 28, 2018
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.