3.5.0 and later
Microsoft Service Bus Connector Release Notes - Mule 3
Support Category: Select
To implement message integration scenarios with Microsoft Azure, use the Microsoft Azure Service Bus Connector
1.3.7
February 26, 2020
Compatibility
Application/Service | Version |
---|---|
Mule |
|
Anypoint Studio |
Studo 6.x and later |
Microsoft Azure Storage Client SDK |
5.0.0 |
Service Bus |
|
Connector DevKit |
3.9.7 |
Fixed Issues
Fixed compatibility issues with Mule Runtime 3.9.4 and REST calls such as Send to Queue, Send to Topic, Create Queue, Create Topic, and so forth. (CONN-4808)
Starting with this version, to enable logging for REST request and responses, add this AsyncLogger
statement in the Loggers
block inside the log4j2.xml
file:
<AsyncLogger name="com.mule.connectors.commons.rest.builder.handler.DefaultResponseHandler"
level="TRACE"/>
1.3.6
1.3.5
December 10, 2019
Compatibility
Application/Service | Version |
---|---|
Mule |
3.5.0 and later |
Anypoint Studio |
Studo 6.x and later |
Service Bus |
|
Connector DevKit |
3.9.7 |
Features
You can now log requests and responses when using this connector. To set up logging:
-
For REST operations, such as Queues list, put this AsyncLogger statement in the Loggers block in the
log4j2.xml
file:<AsyncLogger name="org.mule.modules.microsoftservicebus.interceptor.logging.RestLoggingInterceptor" level="DEBUG" additivity="false">
-
For AMQP operations, such as Topic send, put this AsyncLogger statement in the Loggers block in the
log4j2.xml
file:<AsyncLogger name="org.mule.modules.microsoftservicebus.amqp" level="DEBUG" additivity="false">
1.3.2
February 9, 2018
Fixed: The defined exception strategy was not being used correctly with <microsoftservicebus:queue-receive>
.
When a flow was using a microsoftservicebus:queue-receive
and synchronous processing strategy,
the connector was not using the proper exception strategy to handle the error.
Starting with 1.3.2 the exception strategy set on the flow is invoked if present.
1.3.1
June 9, 2017
A hotfix has been released for the Microsoft Service Bus Connector - version 1.3.1.
Fixed Issues
-
Fixed several threading and synchronization issues encountered when working with synchronous and asynchronous flow strategies by changing how the connector handles these strategies. For the sync scenario, the message is acknowledged only when the flow finishes with success. In case of an error, the message is not acknowledged, and will be consumed until success. For the async scenario, the message is never auto-acknowledged, so it will be re-consumed no matter if the flow fails or is successful. For the message to be acknowledged, a new Acknowledge Message processor must be used in the flow. This processor receives an AmpqMessage as input and acknowledges it.
-
For an example on how to use the Acknowledge Message processor, go to Synchronous and asynchronous behavior section of the user manual
-
1.3.0
April 04, 2017
Fixed Issues
-
The connector now supports sending/receiving large messages(more than 256KB) through Azure Service Bus queues. To enable this functionality a Azure Storage Account is needed, and the connection credentials for this account must be specified under the Azure Service Bus Connection Strategy. If these credentials are specified then the storage is used to store as a blob every message body sent through the queues using the specific Connection Strategy. When you’re expecting to receive large messages the Storage credentials must also be specified so the connector can retrieve the message body from the Blob storage and delete the blob afterwards.
-
Improved the connection management to prevent a potential deadlock issue.
-
Fixed message loss issue when flow was running under Async processing strategies.
-
Exposed additional metadata via DataSense
-
Improved Demo packages including web forms to publish new messages to queues or topics.
1.0.0
January 21, 2015
We are pleased to release a new connector for Service Bus. The ServiceBus connector v1.0 enables Windows Service Bus on-premises, or Azure Service Bus cloud-hosted reliable messaging integration scenarios. Support for queues, topics and event hubs is provided, with messages being sent or received via the AMQP 1.0 transport. Dynamic discovery and provisioning of Service Bus objects is possible via the built-in management API.