Nav

Anypoint MQ Connector Release Notes

August 2017

To support Exchange 2.0 properly, the feature ID of Anypoint MQ Connector has changed. Before you download v1.2.0 from Exchange 2.0, uninstall the existing version of this connector in Studio.

This release of the Anypoint MQ Connector lets you add messaging access to Anypoint MQ queues and exchanges from Anypoint Studio applications.

See Also:

Compatibility

Software Version

Mule Runtime

3.7.4 and newer

Anypoint Studio

5.4.n

Version 1.2.0 - August 23, 2017

To support Exchange 2.0 the ID of the connector in Anypoint Studio changed to org.mule.tooling.ui.extension.mule-transport-amqp-tooling.3.5.0.feature.group - because of this change, version 3.7.2 does not appear as an update in the Connectors Update Site but instead appears as a new connector. Please uninstall your existing Anypoint MQ Connector if the version is v1.1.3 or older in Studio before you install v1.2.0

Version 1.1.3 - July 28, 2017

This version was for internal bug fixes and to fix this issue:

  • SE-4976 - MUnit gives an null pointer exception when run against a project containing an MQ endpoint.

Version 1.1.2 - May 9, 2017

This release fixes these issues:

Issue Description

SE-5739

Default clientMode in Anypoint MQ connector still setting MULE as the default.

SE-5700

Anypoint MQ service unavailable.

SE-5680

Anypoint MQ subscriber does not honor the scheduleAtFixedRate from the schedule service.

Version 1.1.1 - March 27, 2017

Important: This version was removed from our repositories due to a bug affecting the MQ platform. If you use this version, you should upgrade to a newer version as soon as possible to avoid affecting you or other MQ customers.

Anypoint MQ connector version 1.1.1 changes the default connection mode. The current Client Mode (or XML clientMode) changes in this release to SYNC as the default. The MULE value has been deprecated in version 1.1.1 and is being removed in the next version - until the next version, the MULE value is still available.

Issue Description

SE-5503

Refine the error message when publishing to Anypoint MQ fails

SE-5286

MQ subscriber getting timeouts

SE-5221

AbstractCourierRestClient.getAccessToken blocking all threads

SE-5167

MQ subscriber disconnect after several 504 errors

Version 1.1.0 - December 6, 2016

Anypoint MQ connector version 1.1.0 release includes the following bug fixes and improvements:

  • MQ-564: Fixes to support “None” Acknowledgement mode when using the Anypoint MQ connector

  • SE-4433: Fixes to MQ connector to correct failures with “Manual” Acknowledgement mode

  • SE-4189: Fixes to support the MUnit test suite for the Anypoint MQ connector

  • SE-4575: Fixes to honor the ACK timeout period

  • SE-4378: Fix message redelivery exception with Mule Runtime 3.8.1

  • SE-4468: Fix MQ broker error caused by a race condition on the authorization token under heavy load

  • SE-4793: Fixes to de-duplicate user agent and authorization headers

Known Issue:

Anypoint MQ connector does not install when the connector is downloaded using the Anypoint Exchange window launched from Anypoint Studio. Instead use Help > Install New Software > Work with > Anypoint Connectors Update Site. Click Community > Anypoint MQ to download and install the Anypoint MQ connector.

Version 1.0.2 - September 10, 2016

The ACK for NONE now works correctly. For more information, see Acknowledgement Modes.

Version 1.0.1 - April 5, 2016

Fixed in this release:

Issue Description

MQ-383

Tool tips have been added to Anypoint Studio for Anypoint MQ connector.

MQ-379

Fixed issue with MQ connector when there are multiple MQ configurations.

MQ-378

The default value for Max redelivery count is set to -1 (infinite retries).

MQ-365

Setting of timeout mid flow is allowed.

MQ-364

An Invalid MQ subscriber used in an application flow causes the application to throw errors and prevent start of application.

MQ-363

An Invalid MQ destination used in an application flow causes the application to throw errors and prevent start of application.

MQ-353

Publish operation overrides all Mule event content.

SE-3473

Fixed issue with connector that caused MQ subscribers to randomly stop retrieving the message in scenarios involving slow instances and queues without any messages.

Known Issues

  • The Anypoint MQ connector currently doesn’t support tracking.

    Example with tracking:

    
                
             
    1
    2
    3
    4
    
    <flow name="customers-all-get" tracking:enable-default-events="true">
      <anypoint-mq:subscriber config-ref="Anypoint_MQ_Configuration" destination="testQueue" acknowledgementMode="AUTO"/>
      <tracking:transaction id="customers-all-get"/>
    </flow>

    This is the same example with the subscriber tracking statement removed:

    
                
             
    1
    2
    3
    
    <flow name="customers-all-get">
      <anypoint-mq:subscriber config-ref="Anypoint_MQ_Configuration" destination="testQueue" acknowledgementMode="AUTO"/>
    </flow>