---
schema_version: "1"
id: 9f541bed24cebff66ee789a7642e660e6131627258a593b3961a3d960e2c7464
title: AMQP Connector Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/connector/connector-amqp.md
canonical_url: https://docs.mulesoft.com/release-notes/connector/connector-amqp
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 842408140331e7f90fea421440a93d56f0e2017e5c8f12bd31d8cb5391fddc83
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
---

# AMQP Connector Release Notes

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Support Category:
[Select](https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/legal/Agreements/versioning-back-support-policy.pdf)

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](https://docs.mulesoft.com/amqp-connector/latest/)

## 1.9.5

**October 13, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.3.0 and later</p></td></tr><tr><td><p>RabbitMQ AMQP client library</p></td><td><p>5.37.0</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The RabbitMQ AMQP client library is upgraded to version 5.37.0 to address reported security vulnerabilities.</p></td><td><p>W-24409879</p></td></tr></tbody></table>

## 1.9.4

**September 18, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.3.0 and later</p></td></tr><tr><td><p>RabbitMQ AMQP client library</p></td><td><p>5.36.0</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The RabbitMQ AMQP client library is upgraded to version 5.36.0 to address reported security vulnerabilities.</p></td><td><p>W-24142423</p></td></tr></tbody></table>

## 1.9.3

**September 3, 2026**

### What’s New

- This release includes general security fixes.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.3.0 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.34.0</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

## 1.9.2

**August 10, 2026**

### What’s New

- This connector version requires Mule runtime 4.6.22 or later if you’re using Mule 4.6.x, or Mule
  runtime 4.9.9 or later if you’re using Mule 4.9.x. If you prefer not to upgrade your Mule runtime,
  use the connector version released immediately after this one.

- The RabbitMQ AMQP client library is upgraded to 5.34.0.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.3.0 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.34.0</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>AMQP Connector no longer leaks consumers on the message listener across broker reconnection cycles.</p></td><td><p>W-22860958</p></td></tr><tr><td><p>AMQP Connector now correctly verifies the broker hostname when using mutual TLS and maps oversized inbound messages to a connectivity error instead of failing unexpectedly.</p></td><td><p>W-23481127</p></td></tr></tbody></table>

## 1.9.1

**July 21, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.3.0 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.31.0</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>AMQP Connector now raises the <code>AMQP:EXCHANGE_NOT_FOUND</code> error instead of silently dropping the message when the configured returned-message exchange doesn’t exist on the broker.</p></td><td><p>W-20742724</p></td></tr></tbody></table>

## 1.9.0

**November 14, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.3.0 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.22.0</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>AMQP Connector now has the new <strong>Max Inbound Message Body Size</strong> field, which controls the maximum allowed message size processed.</p></td><td><p>W-17660592</p></td></tr><tr><td><p>AMQP Connector no longer fails with the <code>Unable to Commit transaction, the TX Channel doesn’t exist</code> error when mixing non-transactional and transactional flows when using the <strong>Publish</strong> operation.</p></td><td><p>W-20120112</p></td></tr><tr><td><p>AMQP Connector now properly handles null header transformation when running in Java 17.</p></td><td><p>W-19239339</p></td></tr></tbody></table>

## 1.8.3

**July 11, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.3.0 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.22.0</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>AMQP Connector is now backward compatible with 1.7.x by parameter reordering.</p></td><td><p>W-18402047</p></td></tr><tr><td><p>AMQP Connector now properly disposes of idle channels.</p></td><td><p>W-18832287</p></td></tr></tbody></table>

## 1.8.2 (Deprecated)

**April 15, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.3.0 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.22.0</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>Improved the channel management logic in concurrent scenarios by introducing a <code>ChannelPool</code> mechanism. This resolves issues with <code>requestBrokerConfirms="true"</code> in <strong>Publish</strong> operations.</p></td><td><p>W-17035109</p></td></tr><tr><td><p>The AMQP <strong>Listener</strong> source no longer triggers an <code>IllegalAccessException</code> when trying to access certain message headers through an expression language, for example <code>attributes.headers</code>. The connector now safely accesses these values through supported APIs.</p></td><td><p>W-16433857</p></td></tr></tbody></table>

## 1.8.1 (Deprecated)

**October 2, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.3.0 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.22.0</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The RabbitMQ client library is upgraded to 5.22.0.</p></td><td><p>W-16732133</p></td></tr></tbody></table>

## 1.8.0 (Deprecated)

**May 31, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.18.0</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>Use the new <strong>Skip exchange validation</strong> field in the <strong>Publish</strong> operation to skip the exchange validation. Additionally, the <strong>Publish</strong> operation now uses a single channel for each request, rather than creating a new channel each time.</p></td><td><p>W-15539673</p></td></tr></tbody></table>

## 1.7.7

**December 15, 2023**

### What’s New

- This connector is now compatible with Java 17.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.18.0</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

## 1.7.6

**December 5, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.18.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>AMQP Connector now generates ACK IDs with a unique identifier to avoid collisions.</p></td><td><p>W-14210002</p></td></tr></tbody></table>

## 1.7.5

**November 14, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.16.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>AMQP Connector no longer creates more than one channel or consumer in RabbitMQ when there is a force closed connection.</p></td><td><p>W-13862304</p></td></tr></tbody></table>

## 1.7.4

**April 19, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr><tr><td><p>RabbitMQ Client Library</p></td><td><p>5.16.0</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>AMQP consumers now do not get disposed after a failed deployment when an AMQP Connector configuration is shared in a Mule domain.</p></td><td><p>W-10706136</p></td></tr></tbody></table>

## 1.7.3

**December 22, 2021**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The AMQP <strong>Listener</strong> source failed with the error <code>TX Channel doesn’t exist</code> when a transaction initiated from a message source was rolled back.</p></td><td><p>AMQPC-24</p></td></tr></tbody></table>

## 1.7.2

**August 31, 2021**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Application/Service</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.1.1 and later</p></td></tr></tbody></table>

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue</th><th>ID</th></tr></thead><tbody><tr><td><p>The <strong>Reject</strong> operation could not requeue messages.</p></td><td><p>AMQPC-22</p></td></tr></tbody></table>

## 1.7.1

**June 9, 2021**

### New Features and Enhancements

None

### Fixed Issues

- Fixed an issue in which the **Publish consume** operation leaked channels. (AMQPC-20)

## 1.7.0

**December 29, 2020**

### New Features and Enhancements

None

### Fixed Issues

- Added mTLS support. (AMQPC-14)

## 1.6.5

**December 15, 2020**

### New Features and Enhancements

None

### Fixed Issues

- Fixed the behavior that prevented the correct acknowledgment of processed messages when the
  application shut down. (AMQPC-12)

## 1.6.4

**September 21, 2020**

### New Features and Enhancements

None

### Fixed Issues

- Fixed an issue in which inflight messages were not acknowledged during the runtime shutdown.
  (AMQPC-12)

## 1.6.3

**August 6, 2020**

### New Features and Enhancements

None

### Fixed Issues

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

## 1.6.2

**April 20, 2020**

### New Features and Enhancements

None

### Fixed Issues

Define queue bindings to an exchange in queue declarations, as in Mule 3. (AMQP-138)  
To define queue bindings, use the Binding Routing Key parameter in the Queue Definition.

## 1.6.1

This version was not released.

## 1.6.0

**February 26, 2020**

### New Features and Enhancements

- The timestamp attribute is now in the `amqp:properties` element.

- You can now set the `messageid` attribute in the publish-consume operation.

### Fixed Issues

- AMQP Connector did not apply the expiration property value. (MULE-18012)

- The timestamp attribute did not appear in the 'amqp:properties' element.

- The `messageid` attribute could not be set in the publish-consume operation. (AMQP-158)

## 1.5.0

**December 18, 2019**

### New Features and Enhancements

- Added a handshake configuration to configuration parameters (AMQP-157)

- Added the ability to set socket attributes for AMQP (AMQP-156)

## 1.4.5

**September 3, 2019**

### Fixed Issues

- Leak in dynamic config: AmqpConfig POJOs do not implement equals and hashcode. (AMQP-152)

- `ConnectionException` is not thrown when the queue is not found. (AMQP-151)

- Use `basicReject` or `basicAck` for cases where brokers are recovered and `recoverStrategy` is set
  to `NO_REQUEUE`. (AMQP-150)

## 1.4.4

**July 31, 2019**

### Fixed Issues

- Channel leak in publish-consume operation. (AMQP-145)

- Default TLS context should be available for a TLS connection. (AMQP-146)

- AMQP Connector Publish operation incorrectly sets the delivery mode for sent messages. (AMQP-148)

## 1.4.3

**May 31, 2019**

### Fixed Issues

- Consumer Manager does not stop consumers separately when configuring a domain. (AMQP-142)

## 1.4.2

**March 27, 2019**

### Fixed Issues

- Race condition with consumer regeneration and Mule redeploy in domain. (AMQP-140)

- Default Exchange is not taken into account in publish. (AMQP-141)

## 1.4.1

**March 14, 2019**

### Fixed Issues

- Operations do not close channel on MANUAL ack mode. (AMQP-139)

## 1.4.0

**March 8, 2019**

### New Features and Enhancements

- Defines queues bindings to exchange in queues declarations as in Mule 3. (AMQP-138)

## 1.3.4

**February 11, 2019**

### Fixed Issues

- Enforce reconnection when an AlreadyClosed exception occurs and when the reason is not identified
  for a fallback address. (AMQP-133)

## 1.3.3

**February 5, 2019**

### Fixed Issues

- Always enforce reconnection to be performed: guarantee reconnection when consumers are cancelled.
  (AMQP-132)

## 1.3.2

**January 30, 2019**

### Fixed Issues

- Move Generic Connection Provider to AmqpConfig so that the connection is bound to the
  configuration. (AMQP-131)

## 1.3.1

**January 29, 2019**

### Fixed Issues

- Disabling RabbitMQ NIO functionality. (AMQP-127)

- Problem connecting to fallbackAddresses - always the last address was attempted. (AMQP-126)

## 1.3.0

**January 21, 2019**

### New Features and Enhancements

- Reincorporate fallback addresses in AMQP 4 connector. (AMQP-115)

## 1.2.0

**January 8, 2019**

### New Features and Enhancements

- User should be able to set the requestedHeartbeat in the connector. (AMQP-114)

## 1.1.3

**December 19, 2018**

### Fixed Issues

- Consumers are not released when associated to a connector defined in a domain. (AMQP-113)

## 1.1.2

**November 27, 2018**

### Fixed Issues

- AMQP client ShutdownSignalExceptions must be handled in listeners. (AMQP-107)

## 1.1.1

**October 29, 2018**

### Fixed Issues

- Transformer service incorrectly transformed byte array. (AMQP-105)

## 1.1.0

**October 16, 2018**

### New Features and Enhancements

- SNI Support.

- Performance improvements.

- Use of NIO RabbitMQ client API.

### Fixed Issues

- AMQP module ignores quality of service in listener. (AMQP-102)

## 1.0.2

**October 29, 2018**

### Fixed Issues

- transformer service incorrectly transforms byte array. (AMQP-105)

## 1.0.1

**October 16, 2018**

### New Features and Enhancements

- Performance improvements.

- Use of NIO rabbitmq client API.

### Fixed Issues

- AMQP module ignores quality of service in listener. (AMQP-102)

**May 2018**

## 1.0.0

**May 24, 2018**

### New Features and Enhancements

Initial Release.

### Upgrade Requirements

Mule 4.1

## See Also

- [Salesforce Help](https://help.salesforce.com)

- [MuleSoft Services](https://www.mulesoft.com/support-and-services)

- [Known Issues](https://help.salesforce.com/s/issues)