---
schema_version: "1"
id: 945f4d21a3a7e8ca6852cfa0ac6f71645959e631bda9737f5809ac1f626fd9d6
title: JMS Connector Release Notes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/release-notes/connector/connector-jms.md
canonical_url: https://docs.mulesoft.com/release-notes/connector/connector-jms
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 3ad3ce51e29ef68f933f521395d183508f11a81ce1576f163fc26d6450c5b5ec
description: MuleSoft Documentation Site
latest: true
---
---
product: Release Notes
version: master
---

# JMS 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 JMS (Java Message Service) (JMS Connector) enables sending and receiving
messages to queues and topics for any message service that implements the JMS specification.

Guide: [JMS Connector User Guide](https://docs.mulesoft.com/jms-connector/latest/)

## 2.0.2

**October 14, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.10.0 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>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><div><div><p>This release includes general security fixes.</p></div></div></td><td><p>W-24471767</p></td></tr></tbody></table>

## 2.0.1

**September 24, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.10.0 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>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><div><div><p>A non-transactional JMS publish operation no longer hangs indefinitely when the JMS broker stops responding during session creation. The operation now fails as a connectivity error so the configured reconnection strategy can recover.</p></div></div></td><td><p>W-18913222</p></td></tr><tr><td><div><div><p>JMS listener and consumer creation no longer hang indefinitely when the JMS provider blocks during failover. The operation now reports a connectivity error so the configured reconnection strategy can recover.</p></div></div></td><td><p>W-22932102</p></td></tr><tr><td><div><div><p>JMS connection errors are now routed only to listeners consuming the affected destination, preventing a destination-specific failure from disrupting listeners on other destinations that share the same configuration.</p></div></div></td><td><p>W-23286173</p></td></tr><tr><td><div><div><p>JMS broker connections are now opened lazily in transactional and XA connection paths, preventing connections from being created and discarded during connection setup.</p></div></div></td><td><p>W-22790737</p></td></tr><tr><td><div><div><p>The Spring framework is upgraded to version 6.2.19.</p></div></div></td><td><p>W-24129987</p></td></tr></tbody></table>

## 2.0.0

**August 4, 2026**

### What’s New

- This connector is now compatible with Java 17 only.

- The **Enable xa** field is removed from the ActiveMQ connection factory configuration.

- JMS Connector provides separate connection types for XA and non-XA transactions. You can now
  select the new **ActiveMQ XA Connection** or **Generic XA Connection** type in the **JMS Config**
  window. These new connection types replace the previous **Enable xa** toggle on a single
  connection.

- The deprecated **ActiveMQ Connection - No Connectivity Test** connection type is removed. There is
  no replacement connection type. Use **ActiveMQ Connection** instead.

For more information about how to upgrade the connector to version 2.0, refer to
[Upgrading and Migrating JMS Connector to Version 2.x](https://docs.mulesoft.com/jms-connector/latest/jms-connector-upgrade-migrate).

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.10.0 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>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><div><div><p>These libraries are upgraded:</p></div><div><ul><li><p>The <code>jakarta.jms-api</code> library is upgraded to version 3.1.0, replacing <code>javax.jms-api</code>.</p></li><li><p>The Spring framework is upgraded to version 6.2.15.</p></li><li><p>The Apache ActiveMQ library is upgraded to version 6.1.0.</p></li><li><p>The Apache ActiveMQ Artemis library is upgraded to version 2.50.0.</p></li></ul></div></div></td><td><p>W-22761813</p></td></tr></tbody></table>

## 1.10.6

**September 3, 2026**

### What’s New

- This release includes general security fixes.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.2.0 and later</p></td></tr><tr><td><p>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

## 1.10.5

**August 12, 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.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.2.0 and later</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><div><div><p>A JMS connection that uses an invalid or duplicate client ID now fails immediately as a terminal error instead of retrying indefinitely, and the associated connection is closed to prevent a thread leak.</p></div></div></td><td><p>W-19332327</p></td></tr><tr><td><div><div><p>Blocking session and consumer creation calls to an unresponsive broker are now bounded by a configurable timeout (default 30 seconds) and surface a connectivity error so the configured reconnection strategy can recover, instead of hanging indefinitely.</p></div></div></td><td><p>W-22932102</p></td></tr><tr><td><div><div><p>A JMS exception that names a single registered destination is now routed only to that destination’s listeners, so unrelated listeners no longer receive the error.</p></div></div></td><td><p>W-23286173</p></td></tr><tr><td><div><div><p>JMS threads are now properly closed and cleaned up during application undeployment, preventing a thread leak when using the ActiveMQ and Artemis drivers.</p></div></div></td><td><p>W-18053810</p></td></tr></tbody></table>

## 1.10.4

**July 23, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.2.0 and later</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>A non-transactional JMS publish operation no longer hangs indefinitely when the JMS broker stops responding during session creation. The operation now fails as a connectivity error so the configured reconnection strategy can recover.</p></td><td><p>W-18913222</p></td></tr><tr><td><p>Oracle Advanced Queuing (AQ) publish failures that report a connection timeout are now treated as connectivity errors, instead of terminal publishing errors, so the configured reconnection strategy can recover.</p></td><td><p>W-20264223</p></td></tr></tbody></table>

## 1.10.3

**January 30, 2026**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.2.0 and later</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>Updated commons-io from 2.15.0 to 2.21.0.</p></td><td><p>W-20834191</p></td></tr><tr><td><p>Updated commons-lang3 from 3.12.0 to 3.20.0.</p></td><td><p>W-20834191</p></td></tr><tr><td><p>Updated com.google.guava:guava from 32.1.3-jre to 33.5.0-jre.</p></td><td><p>W-20834191</p></td></tr><tr><td><p>Updated com.fasterxml.jackson:jackson from 2.14.2 to 2.15.0.</p></td><td><p>W-20834191</p></td></tr></tbody></table>

## 1.10.2

**June 30, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.2.0 and later</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>Updated org.apache.activemq:activemq-client from 5.16.7 to 5.16.8.</p></td><td><p>W-18223618</p></td></tr><tr><td><p>Updated com.google.guava:guava from 32.1.2-jre to 32.1.3-jre.</p></td><td><p>W-18223618</p></td></tr><tr><td><p>Updated org.mule.runtime:mule-sdk-api from 0.8.0 to 0.8.6.</p></td><td><p>W-18223618</p></td></tr></tbody></table>

## 1.10.1

**April 11, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</th><th>Version</th></tr></thead><tbody><tr><td><p>Mule</p></td><td><p>4.2.0 and later</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>JMS Connector now contains patched Spring 5.x to fix security vulnerabilities.</p></td><td><p>W-18198070</p></td></tr></tbody></table>

## 1.10.0

**March 20, 2025**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>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>JMS Connector now supports query parameters in failover URLs for ActiveMQ connection configurations.</p></td><td><p>W-17286858</p></td></tr><tr><td><p>This release includes general security fixes.</p></td><td><p>W-17849663</p></td></tr><tr><td><p>JMS Connector now has a system property to set a delay in releasing resources, which helps prevent thread leaks when using Artemis as the JMS driver.</p></td><td><p>W-17327464</p></td></tr></tbody></table>

## 1.9.7

**August 13, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>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>Message headers now have setters.</p></td><td><p>W-16116454</p></td></tr></tbody></table>

## 1.9.6

**June 28, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>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 connector no longer sets the <strong>verifyHostName</strong> property for ActiveMQ Client versions prior to 5.15.6.</p></td><td><p>W-15122911</p></td></tr><tr><td><p>Connections with <strong>Failover</strong> configuration now support the <strong>verifyHostName</strong> parameter when the version of the ActiveMQ Client requires it.</p></td><td><p>W-15122911</p></td></tr></tbody></table>

## 1.9.5

**June 14, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>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>Reconnection on publish when using Weblogic now works correctly.</p></td><td><p>W-15804613</p></td></tr><tr><td><p>Reconnection on consume when using Weblogic and Artemis now works correctly.</p></td><td><p>W-15837781</p></td></tr></tbody></table>

## 1.9.4

**May 8, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>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>Reconnection when using Artemis Server now works correctly.</p></td><td><p>W-15211060</p></td></tr></tbody></table>

## 1.9.3

**January 19, 2024**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>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>Thread leaks no longer occur when a reconnection is triggered.</p></td><td><p>W-14282515</p></td></tr></tbody></table>

## 1.9.2

**January 4, 2024**

### What’s New

- This connector is now compatible with Java 17.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>OpenJDK</p></td><td><p>8, 11, and 17</p></td></tr></tbody></table>

## 1.9.1

**November 29, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>OpenJDK</p></td><td><p>8 and 11</p></td></tr></tbody></table>

### What’s New

- The `org.apache.activemq:activemq-client` library support is upgraded to version 5.15.16 to
  address reported security vulnerabilities.

- SSL connections set **verifyHostName** to `false` by default to keep backwards compatibility.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>The ActiveMQ client is no longer affected by a malicious ActiveMQ broker.</p></td><td><p>W-14544171</p></td></tr><tr><td><p>TLS connections now require to set <strong>verifyHostName</strong> on the ActiveMQ client.</p></td><td><p>W-14544171</p></td></tr></tbody></table>

## 1.9.0

**August 18, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>JDK</p></td><td><p>8</p></td></tr></tbody></table>

### What’s New

- The `com.google.guava` library is upgraded to version 32.1.2-jre to address reported security
  vulnerabilities.

### Fixed Issues

<table><colgroup><col> <col></colgroup><thead><tr><th>Issue Resolution</th><th>ID</th></tr></thead><tbody><tr><td><p>You can now enable a secure connection for the <strong>Generic Connection</strong>.</p></td><td><p>W-13830306</p></td></tr><tr><td><p>The <code>com.google.guava</code> library is upgraded to version 32.1.2-jre to address reported security vulnerabilities.</p></td><td><p>W-13880316</p></td></tr></tbody></table>

## 1.8.8

**April 05, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>JDK</p></td><td><p>8</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>Bumped spring-jms to version 5.3.26 at JMS Connector to address vulerabilities for spring-jms lower versions.</p></td><td><p>W-12950397</p></td></tr></tbody></table>

## 1.8.7

**January 18, 2023**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>JDK</p></td><td><p>8</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 JMS Connector <strong>Publish operation</strong> no longer fails reconnecting on <strong>ConnectionFailedException</strong>.</p></td><td><p>W-12302934</p></td></tr></tbody></table>

## 1.8.6

**November 02, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>JDK</p></td><td><p>8</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 JMS Connector <strong>Consume operation</strong> no longer duplicates messages when the operation stops consuming messages.</p></td><td><p>W-11786899</p></td></tr><tr><td><p>The JMS Connector <strong>Consume operation</strong> now stops correctly when it stops consuming messages.</p></td><td><p>W-11853709</p></td></tr></tbody></table>

## 1.8.5

**October 31, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>JDK</p></td><td><p>8</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>JMS Connector now uses correctly an SSL connection with Active MQ and XA.</p></td><td><p>W-11786346</p></td></tr></tbody></table>

## 1.8.4

**June 3, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>JDK</p></td><td><p>8</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>SessionCacheSize behavior now has impact on the total number of sessions that the connector creates.</p></td><td><p>W-11056232</p></td></tr><tr><td><p>Updated spring-jms to version 5.3.20 to address vulnerabilities for lower spring-jms versions.</p></td><td><p>W-11157710</p></td></tr></tbody></table>

## 1.8.3

**Apr 20, 2022**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>JDK</p></td><td><p>8</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>Fixed JMS Connector concurrency limitation for the <strong>Consume</strong> operation.</p></td><td><p>W-10685928</p></td></tr></tbody></table>

## 1.8.2

**Dec 21, 2021**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>JDK</p></td><td><p>8</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>Fixed Bitronix errors when a TransactionException occurs.</p></td><td><p>JMSCLI-26]</p></td></tr></tbody></table>

## 1.8.1

**Nov 4, 2021**

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>JDK</p></td><td><p>8</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>Reconnection did not work when using TLS because <code>SslContext</code> was lost between reconnection attempts.</p></td><td><p>JMSC-93</p></td></tr></tbody></table>

## 1.8.0

**Oct 18, 2021**

### What’s New

- Added a new connection provider for ActiveMQ that does not perform pre-deployment connectivity
  testing, which avoids subscribing to topics with durable connections in simultaneous cloud
  deployments.

### Compatibility

<table><colgroup><col> <col></colgroup><thead><tr><th>Software</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>JDK</p></td><td><p>8</p></td></tr></tbody></table>

## 1.7.5

**May 06, 2021**

### Fixed Issues

- A thread leaked when connections were validated on Mule runtime. (JMSCLI-20)

## 1.7.4

**April 14, 2021**

### Fixed Issues

- Fixed an issue that caused the transaction error **A transaction is not available** when trying to
  publish a message inside of an Async scope component. (JMSC-83)

- When performing an ACK or session recover over a message read using the **Consume** operation,
  with the ACK mode set to **MANUAL**, an `The Consumer is closed` error was thrown. (JMSCLI-16)

- Fixed the issue that caused leaked connections when using dynamic parameters in the JMS Connector
  configuration. (JMSC-84)

## 1.7.3

**January 13, 2021**

### Fixed Issues

Fixed a session leak that happened when listening to an inexistent queue. (JMSCLI-12)

## 1.7.2

**January 7, 2021**

### Fixed Issues

Fixed a reconnection issue that occurred when an exception was thrown while publishing. (JMSCLI-10)

## 1.7.1

**August 12, 2020**

### Fixed Issues

Fixed a connection leak that occurred when using DataWeave expressions on the connector
configuration. (JMSC-70)

## 1.7.0

**June 8, 2020**

### Features

- Added support to avoid automatic reply when the inbound message contains a ReplyTo header.
  (JMSC-65)

- Renamed the Listener operation to On New Message. (JMSC-68)

## 1.6.3

**October 15, 2019**

### Known Issues

The `max-redelivery` parameter cannot be configured on the connector side, as it has no effect. It
must be configured on the broker side.

### Fixed Issues

- Fixed a bug that made apps fail to deploy, even when configured with `failsDeployment="false"`.
  (MULE-17602)

## 1.6.2

**August 9, 2019**

### Fixed Issues

- JMS Connector now honors payload encoding when publishing message to a JMS queue. (MULE-17286)

## 1.6.0

**June 13, 2019**

### Features

- Added support for different [request reply patterns](https://docs.mulesoft.com/jms-connector/latest/) for the
  **Publish Consume** and **Listener** operations.

## 1.5.1

**June 12, 2019**

### Fixed Issues

- The JMS Consume operation didn’t roll back correctly on XA transactions. (MULE-16969)

- The JMS Bridge with XA hangs in some cases.

## 1.5.0

**May 29, 2019**

### Features

- Make XA pool configurable in the JMS connector. (MULE-16926)

### Fixed Issues

- JMS Publish Consumer Operation leaks connection. (MULE-16927)

## 1.4.1

**May 28, 2019**

### Fixed Issues

- Fix issue with reconnection

## 1.4.0

**May 27, 2019**

### Fixed Issues

- Fix issue with XA transactions on reconnection scenarios.

## 1.3.7

**April 17, 2019**

### Features

- Upgraded Spring version from 5.1.5 to 5.1.6.

- Fixed a bug that prevented using XA transactions with some brokers in case of rollbacks.

## 1.3.6

**April 3, 2019**

### Features

- Fixed a bug that prevented the usage of the connector as a proxy for some brokers.

## 1.3.5

**March 19, 2019**

### Features

- Fixed a bug that prevented the reconnection stategy to be triggered in the Publish operation.

## 1.3.4

**February 22, 2019**

### Features

- Added a new icon to the connector.

- Fixed a bug around JNDI lookup destinations

## 1.3.3

**January 14, 2019**

### Features

- Fixed connection leaks. These leaks happened when a Publish action failed internally or when doing
  an automatic ReplyTo when using the "On New Message" source.

## 1.3.2

**November 27, 2018**

### Features

- Fixed a deadlock when using the JMS Listener on too quick flows, which caused listeners to stop
  receiving messages.

### Fixed Issues

- Application hangs after receiving a few messages from ActiveMQ in Mule 4.x. (MULE-16087)

## 1.3.1

**Deprecated**

**October 29, 2018**

### Features

- Fixed issue that prevent the usage of a TLS Context.

### Fixed Issues

- JMS Connector doesn’t initialize the TLS Context if it is defined as a child element. (MULE-15930)

## 1.3.0

**Deprecated**

**August 29, 2018**

### Features

- JMS is Non-Blocking for Publish, Consume, and Publish-Consume Operations, improving the
  scalability of Mule applications.

- Support for XA Transactions. The connector can participate in multi-resource transactions, like
  DB, IBM MQ, and other XA compatible connectors.

- ActiveMQ SSL Configuration Support. ActiveMQ Connections can be configured with SSL/TLS
  Configuration for secure connections.

- JMS Listener. Can now configure how to propagate the Correlation ID on the JMS Listener Response.

### Fixed Issues

- JMS Publish Consume operation throws JmsIllegalBodyException when returning
  ManagedCursorStreamProvider in the payload. (MULE-14852)

- Support JMS Non-Blocking API. (MULE-14875)

- JMS throws ClassCastException when receiving a message. (MULE-15431)

- Add support for SSL in the JMS Connector. (MULE-12341)

- Implement human-readable toString() implementations. (MULE-15477)

- JmsHeaders is not Serializable but JmsAttributes is. (MULE-15455)

- XA: NPE on JmsListener#onError after flow stop. (MULE-15488)

- JMS: Cannot configure sendCorrelationId in a listener, for sending a response. (MULE-15502)

## 1.2.3

**August 7, 2018**

### Fixed Issues

- Fixed issue that prevented receiving messages published through the Artemis Management Console.
  (MULE-15431)

## 1.2.2

**May 7, 2018**

### Features

Minor internal upgrades.

### Fixed Issues

- Update Spring JMS to version 5.0.5.RELEASE. (MULE-14966)

- Upgrade Jackson to 2.9.5. (MULE-14795)

## 1.2.1

**April 11, 2018**

### Features

This release includes the following enhancements, changes, and fixes:

- JMS Listener failed to reply to a destination if the response was provided by a transformation
  inside the `Response Body`.

### Fixed Issues

- JMS Publish Consume operation throws JmsIllegalBodyException when returning
  ManagedCursorStreamProvider in the payload. (MULE-14852)

## 1.2.0

**Mar 26, 2018**

### Features

This release includes the following enhancements, changes, and fixes:

- JMS Listener when running on a cluster only starts in the main node. This setting is configurable:
  `primaryNodeOnly="false"`

### Upgrade Requirements

Mule 4.1.1

### Fixed Issues

- jms:listener should only run on primary node when listening to a topic. (MULE-14678)

- Upgrade Spring JMS to 5.0.4 release. (MULE-14633)

## 1.1.0

**January 19, 2018**

### Features

This release includes the following enhancements, changes, and fixes:

- Added the capability to define allowed packages in ActiveMQ Configuration.

- Added support for message correlation.

- Improved UX.

### Upgrade Requirements

Mule 4.1

### Fixed Issues

- JMS Config - ActiveMQ label incorrectly displayed. (MULE-14105)

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