Microsoft Service Bus Connector Release Notes - Mule 3

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">

The connector now supports DevKit 3.9.7.

Topic subscriptions didn’t take the subscription name into consideration. In past versions, the name was not considered. This caused topics to be incorrectly subscribed. This is fixed in the current version.

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.

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.

Added custom logic to handle non trivial types at message’s properties.

Added option to skip connectivity test at connector’s startup.

Improved performance when sending messages using SAS-based authentication.

Improved reliability and stability with high-load.

Added support to SAS-based authentication (that is, avoid providing username/password at configuration settings).

Fixed message processing and acknowledge to ensure zero message loss high-reliability (that is, at-least-once delivery).

Fixed message’s consumption from partitioned topics.

Improved error message for invalid property types.

Improved message’s production performance by caching connections.

Added support for sending mule outbound properties as custom properties in the AMQP message.

Upgraded qpid dependency to 0.3.2

The connector kept dequeuing message after the Mule application stopped or was undeployed. This has been fixed and the connector now stops dequeuing messages when the Mule application stops or undeploys.