Flex Gateway新着情報
Governance新着情報
Monitoring API ManagerSupport 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:
August 2, 2022
Anypoint MQ Connector version 1.3.9 is available only via Maven. This version is not available on Exchange. |
Software | Version |
---|---|
Mule |
3.7.4 and later |
Anypoint Studio |
5.4.n and later |
Issue Resolution | ID |
---|---|
The Anypoint MQ Connector 1.3.9 subscriber source now correctly consumes messages after a network outage. |
SE-16793, SE-17007, SE-17206 |
February 20, 2019
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.
April 26, 2018
Improved debug logging - log response time from MQ provides more info for the response receieved from MQ.
December 1, 2017
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).
October 5, 2017
Anypoint MQ Connector provides the Select connector support policy.
August 23, 2017
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.
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.
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.
December 6, 2016
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)
September 10, 2016
The ACK for NONE now works correctly. For more information, see Acknowledgement Modes.
April 5, 2016
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)
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>