Nav

Anypoint MQ Connector Release Notes

July 2018

Select

To support Exchange 2.0 properly, the feature ID of Anypoint MQ Connector has changed. Before you download v1.2.0 and later 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:

1.3.4

July 10, 2018

Feature

  • Improved retry logic.

Fixed in this Release

  • Improve Mule 3 Anypoint MQ connector with retry logic and exponential backoff. (MQ-1210)

1.3.3

April 26, 2018

Version 1.3.3 has following fixes and changes:

  • Improved debug logging - log response time from MQ provides more info for the response receieved from MQ.

  • Using Default Lock TTL on the MQ server end queue configuration as the default acknowledgementTimeout in MQ connector did not let the MQ connector override it to 2 minutes by default. (SE-7951)

Compatibility

Software Version

Mule Runtime

3.7.4 and later

Anypoint Studio

5.4.n and later

1.3.2

February 15, 2018

This release provides a bug fix.

Compatibility

Software Version

Mule Runtime

3.7.4 and later

Anypoint Studio

5.4.n and later

Fixed in This Release

  • Publishing a message to Anypoint MQ failed when running an MUnit test case. (SE-6804)

1.3.1

December 11, 2017

This release allows usage of property placeholders for pollingTime, reconnectionWaitTime, reconnectionAttempts, and acknowledgementTimeout, and fixes one issue.

Fixed in This Release

  • Anypoint MQ REST client stopped after "AUTHORIZE AGAINST BROKER". (SE-7294)

1.3.0

December 1, 2017

This release adds these features:

  • New options are available to the prefetch configuration that let you decide how many times prefetch retries its operation before stopping, and how long to wait between each retry.

  • It is now possible to use property placeholders for the following attributes when configuring the MQ connector in a Mule flow: Polling Time (pollingTime), Reconnection Wait Time (reconnectionWaitTime), Reconnection Attempts (reconnectionAttempts), and Acknowledgement Timeout (acknowledgementTimeout).

Compatibility

Software Version

Mule Runtime

3.7.4 and later

Anypoint Studio

5.4.n and later

Fixed Issues

  • Fix connector prefetch onError method to not stop polling if a queue is not found, (MQ-909)

  • Anypoint MQ is not using system properties to configure the pollingTime. (SE-7176)

  • Fixed issues that could cause frequent timeouts when polling for messages. (MQ-876, SE-6811, SE-6353, SE-5670)

1.2.3

October 5, 2017

The Anypoint MQ connector now provides the Select connector support policy.

Fixed in this release - Move MQ connector to the Select support policy. (MQ-752)

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. Uninstall your existing Anypoint MQ Connector if the version is v1.1.3 or older in Studio before you install v1.2.0.

1.1.3

July 28, 2017

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

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

1.1.2

May 9, 2017

This release fixes these issues:

  • Default clientMode in Anypoint MQ connector still setting MULE as the default. (SE-5739)

  • Anypoint MQ service unavailable. (SE-5700)

  • Anypoint MQ subscriber does not honor the scheduleAtFixedRate from the schedule service. (SE-5680)

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.

  • Refine the error message when publishing to Anypoint MQ fails. (SE-5503)

  • MQ subscriber getting timeouts. (SE-5286)

  • AbstractCourierRestClient.getAccessToken blocking all threads. (SE-5221)

  • MQ subscriber disconnect after several 504 errors. (SE-5167)

1.1.0

December 6, 2016

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

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

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

  • Fixes to support the MUnit test suite for the Anypoint MQ connector. (SE-4189)

  • Fixes to honor the ACK timeout period. (SE-4575)

  • Fix message redelivery exception with Mule Runtime 3.8.1. (SE-4378)

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

  • Fixes to de-duplicate user agent and authorization headers. (SE-4793)

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.

1.0.2

September 10, 2016

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

1.0.1

April 5, 2016

Fixed in this release:

  • Tool tips have been added to Anypoint Studio for Anypoint MQ connector. (MQ-383)

  • Fixed issue with MQ connector when there are multiple MQ configurations. (MQ-379)

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

  • Setting of timeout mid flow is allowed. (MQ-365)

  • An Invalid MQ subscriber used in an application flow causes the application to throw errors and prevent start of application. (MQ-364)

  • An Invalid MQ destination used in an application flow causes the application to throw errors and prevent start of application. (MQ-363)

  • Publish operation overrides all Mule event content. (MQ-353)

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

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>