Flex Gateway新着情報
Governance新着情報
Monitoring API ManagerSupport Category: Select
Anypoint Connector for AMQP (AMQP Connector) enables your application to publish and consume messages using an AMQP 0.9.1-compliant broker.
Guide: AMQP Connector User Guide
July 11, 2025
| Application/Service | Version | 
|---|---|
| Mule | 4.3.0 and later | 
| RabbitMQ Client Library | 5.22.0 | 
| OpenJDK | 8, 11, and 17 | 
| Issue Resolution | ID | 
|---|---|
| AMQP Connector is now backward compatible with 1.7.x by parameter reordering. | W-18402047 | 
| AMQP Connector now properly disposes of idle channels. | W-18832287 | 
April 15, 2025
| Application/Service | Version | 
|---|---|
| Mule | 4.3.0 and later | 
| RabbitMQ Client Library | 5.22.0 | 
| OpenJDK | 8, 11, and 17 | 
| Issue Resolution | ID | 
|---|---|
| Improved the channel management logic in concurrent scenarios by introducing a  | W-17035109 | 
| The AMQP Listener source no longer triggers an  | W-16433857 | 
October 2, 2024
| Application/Service | Version | 
|---|---|
| Mule | 4.3.0 and later | 
| RabbitMQ Client Library | 5.22.0 | 
| OpenJDK | 8, 11, and 17 | 
| Issue Resolution | ID | 
|---|---|
| The RabbitMQ client library is upgraded to 5.22.0. | W-16732133 | 
May 31, 2024
| Application/Service | Version | 
|---|---|
| Mule | 4.1.1 and later | 
| RabbitMQ Client Library | 5.18.0 | 
| OpenJDK | 8, 11, and 17 | 
| Issue Resolution | ID | 
|---|---|
| Use the new Skip exchange validation field in the Publish operation to skip the exchange validation. Additionally, the Publish operation now uses a single channel for each request, rather than creating a new channel each time. | W-15539673 | 
December 15, 2023
This connector is now compatible with Java 17.
| Application/Service | Version | 
|---|---|
| Mule | 4.1.1 and later | 
| RabbitMQ Client Library | 5.18.0 | 
| OpenJDK | 8, 11, and 17 | 
December 5, 2023
| Application/Service | Version | 
|---|---|
| Mule | 4.1.1 and later | 
| RabbitMQ Client Library | 5.18.0 | 
| Issue Resolution | ID | 
|---|---|
| AMQP Connector now generates ACK IDs with a unique identifier to avoid collisions. | W-14210002 | 
November 14, 2023
| Application/Service | Version | 
|---|---|
| Mule | 4.1.1 and later | 
| RabbitMQ Client Library | 5.16.0 | 
| Issue Resolution | ID | 
|---|---|
| AMQP Connector no longer creates more than one channel or consumer in RabbitMQ when there is a force closed connection. | W-13862304 | 
April 19, 2022
| Application/Service | Version | 
|---|---|
| Mule | 4.1.1 and later | 
| RabbitMQ Client Library | 5.16.0 | 
| Issue | ID | 
|---|---|
| AMQP consumers now do not get disposed after a failed deployment when an AMQP Connector configuration is shared in a Mule domain. | W-10706136 | 
December 22, 2021
| Application/Service | Version | 
|---|---|
| Mule | 4.1.1 and later | 
| Issue | ID | 
|---|---|
| The AMQP Listener source failed with the error  | AMQPC-24 | 
August 31, 2021
| Application/Service | Version | 
|---|---|
| Mule | 4.1.1 and later | 
| Issue | ID | 
|---|---|
| The Reject operation could not requeue messages. | AMQPC-22 | 
August 6, 2020
Fixed an issue in which messages were lost due to channel reset when the max-retries limit was reached. (AMQPC-9)
Fixed an issue in which the Consume operation leaked channels, after performing consume and ack actions. (AMQPC-10)
Fixed an issue in which the Listener operation did not recover connection when a reconnection strategy was applied. (AMQPC-11)