Contact Free trial Login

Anypoint MQ Release Notes - Mule 3

Support Category: Select

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

Anypoint Connector for Anypoint MQ lets you add messaging access to Anypoint MQ queues and exchanges from Anypoint Studio applications. For Mule 4, see Anypoint Connector for Anypoint MQ Release Notes - Mule 4.

See Also:

1.3.7

May 8, 2019

Compatibility

Software Version

Mule

3.7.4 and later

Anypoint Studio

5.4.n and later

Fixed Issues

  • Incorrect external API warning message about a connection being leaked.

1.3.6

February 20, 2019

Compatibility

Software Version

Mule

3.7.4 and later

Anypoint Studio

5.4.n and later

Fixed Issues

  • Prevented MUnit from providing the mocking service for the Anypoint MQ connector inbound endpoint.

  • Warning log message stating that a connection was leaked.

  • The threading configuration that produced invalid XML when using the wrong namespace.

  • Duplicated messages that occurred when a prefetch subscriber used the default TTL config.

  • XML order generation that occurred when using the Anypoint Studio plugin.

1.3.5

November 1, 2018

This release fixes a bug.

Compatibility

Software Version

Mule

3.7.4 and later

Anypoint Studio

5.4.n and later

Fixed Issues

  • Incorrectly logged WARN 'A connection to https://mq-ap-southeast-2.anypoint.mulesoft.com/ was leaked`. This is now fixed. (SE-9217)

1.3.4

July 10, 2018

Compatibility

Software Version

Mule

3.7.4 and later

Anypoint Studio

5.4.n and later

Updates

  • Improved retry logic.

Fixed Issues

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

1.3.3

April 26, 2018

Updates

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

Fixed Issues

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

Compatibility

Software Version

Mule

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

3.7.4 and later

Anypoint Studio

5.4.n and later

Fixed Issues

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

1.3.1

December 11, 2017

Updates

This release allows use of property placeholders for pollingTime, reconnectionWaitTime, reconnectionAttempts, and acknowledgementTimeout values.

Fixed Issues

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

1.3.0

December 1, 2017

New 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 Anypoint MQ Connector in a Mule flow: Polling Time (pollingTime), Reconnection Wait Time (reconnectionWaitTime), Reconnection Attempts (reconnectionAttempts), and Acknowledgement Timeout (acknowledgementTimeout).

Compatibility

Software Version

Mule

3.7.4 and later

Anypoint Studio

5.4.n and later

Fixed Issues

  • 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)

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

1.2.3

October 5, 2017

Updates

  • Anypoint MQ Connector provides the Select connector support policy.

Fixed Issues

  • Anypoint MQ Connector was incorrectly categorized in Anypoint Studio. (MQ-752)

1.2.0

August 23, 2017

Updates

To support Exchange 2.0, the ID of Anypoint MQ 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 connector if the version is v1.1.3 or older in Studio before you install v1.2.0.

1.1.3

July 28, 2017

Fixed Issues

  • Internal bug fixes.

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

1.1.2

May 9, 2017

Fixed 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.

Updates

This 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.

Fixed Issues

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

  • Anypoint MQ subscriber getting timeouts. (SE-5286)

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

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

1.1.0

December 6, 2016

Fixed Issues

  • Support for “None” Acknowledgement mode when using Anypoint MQ Connector. (MQ-564)

  • Correct failures with “Manual” Acknowledgement mode. (SE-4433)

  • Support the MUnit test suite for Anypoint MQ Connector. (SE-4189)

  • Honor the ACK timeout period. (SE-4575)

  • Message redelivery exception with Mule 3.8.1. (SE-4378)

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

  • De-duplicate user agent and authorization headers. (SE-4793)

Known Issues

Anypoint MQ Connector does not install when it 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 connector.

1.0.2

September 10, 2016

Fixed Issues

1.0.1

April 5, 2016

Fixed Issues

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

  • Issue with Anypoint 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 Anypoint MQ subscriber used in an application flow causes the application to throw errors and prevent start of application. (MQ-364)

  • An Invalid Anypoint 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)

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

Known Issues

  • Anypoint MQ Connector currently doesn’t support tracking.

    Example with tracking:

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

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

Was this article helpful?

💙 Thanks for your feedback!

Leave feedback…

We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used and to tailor advertising. You can read more and make your cookie choices here. By continuing to use this site you are giving us your consent to do this.