--- schema_version: "1" id: afba20894d455ba9cdb6053ee38009babcc5822d1294eb669b858695250dface title: JMS Connector Release Notes collection: mulesoft version: current locale: ja-jp portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/connector/connector-jms.md canonical_url: https://docs.mulesoft.com/jp/release-notes/connector/connector-jms source_site: docs.mulesoft.com content_type: documentation content_hash: 9dfdb67192a29d4c31d43e016ec3931691c32a3f475d049e278aa8ad09974f10 description: MuleSoft Documentation Site latest: true --- # JMS Connector Release Notes 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)2.0.2 **October 14, 2026** ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

This release includes general security fixes.

W-24471767
## [](#2-0-1)2.0.1 **September 24, 2026** ### Compatibility
Software Version

Mule

4.10.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

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.

W-18913222

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.

W-22932102

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.

W-23286173

JMS broker connections are now opened lazily in transactional and XA connection paths, preventing connections from being created and discarded during connection setup.

W-22790737

The Spring framework is upgraded to version 6.2.19.

W-24129987
## [](#2-0-0)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
Software Version

Mule

4.10.0 and later

OpenJDK

17
### Fixed Issues
Issue Resolution ID

These libraries are upgraded:

  • The jakarta.jms-api library is upgraded to version 3.1.0, replacing javax.jms-api.

  • The Spring framework is upgraded to version 6.2.15.

  • The Apache ActiveMQ library is upgraded to version 6.1.0.

  • The Apache ActiveMQ Artemis library is upgraded to version 2.50.0.

W-22761813
## [](#1-10-6)1.10.6 **September 3, 2026** ### What’s New - This release includes general security fixes. ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
## [](#1-10-5)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
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

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.

W-19332327

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.

W-22932102

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.

W-23286173

JMS threads are now properly closed and cleaned up during application undeployment, preventing a thread leak when using the ActiveMQ and Artemis drivers.

W-18053810
## [](#1-10-4)1.10.4 **July 23, 2026** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

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.

W-18913222

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.

W-20264223
## [](#1-10-3)1.10.3 **January 30, 2026** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Updated commons-io from 2.15.0 to 2.21.0.

W-20834191

Updated commons-lang3 from 3.12.0 to 3.20.0.

W-20834191

Updated com.google.guava:guava from 32.1.3-jre to 33.5.0-jre.

W-20834191

Updated com.fasterxml.jackson:jackson from 2.14.2 to 2.15.0.

W-20834191
## [](#1-10-2)1.10.2 **June 30, 2025** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Updated org.apache.activemq:activemq-client from 5.16.7 to 5.16.8.

W-18223618

Updated com.google.guava:guava from 32.1.2-jre to 32.1.3-jre.

W-18223618

Updated org.mule.runtime:mule-sdk-api from 0.8.0 to 0.8.6.

W-18223618
## [](#1-10-1)1.10.1 **April 11, 2025** ### Compatibility
Software Version

Mule

4.2.0 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

JMS Connector now contains patched Spring 5.x to fix security vulnerabilities.

W-18198070
## [](#1-10-0)1.10.0 **March 20, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

JMS Connector now supports query parameters in failover URLs for ActiveMQ connection configurations.

W-17286858

This release includes general security fixes.

W-17849663

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.

W-17327464
## [](#1-9-7)1.9.7 **August 13, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Message headers now have setters.

W-16116454
## [](#1-9-6)1.9.6 **June 28, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

The connector no longer sets the verifyHostName property for ActiveMQ Client versions prior to 5.15.6.

W-15122911

Connections with Failover configuration now support the verifyHostName parameter when the version of the ActiveMQ Client requires it.

W-15122911
## [](#1-9-5)1.9.5 **June 14, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Reconnection on publish when using Weblogic now works correctly.

W-15804613

Reconnection on consume when using Weblogic and Artemis now works correctly.

W-15837781
## [](#1-9-4)1.9.4 **May 8, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Reconnection when using Artemis Server now works correctly.

W-15211060
## [](#1-9-3)1.9.3 **January 19, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
### Fixed Issues
Issue Resolution ID

Thread leaks no longer occur when a reconnection is triggered.

W-14282515
## [](#1-9-2)1.9.2 **January 4, 2024** ### What’s New - This connector is now compatible with Java 17. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17
## [](#1-9-1)1.9.1 **November 29, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11
### 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
Issue Resolution ID

The ActiveMQ client is no longer affected by a malicious ActiveMQ broker.

W-14544171

TLS connections now require to set verifyHostName on the ActiveMQ client.

W-14544171
## [](#1-9-0)1.9.0 **August 18, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### What’s New - The `com.google.guava` library is upgraded to version 32.1.2-jre to address reported security vulnerabilities. ### Fixed Issues
Issue Resolution ID

You can now enable a secure connection for the Generic Connection.

W-13830306

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

W-13880316
## [](#1-8-8)1.8.8 **April 05, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

Bumped spring-jms to version 5.3.26 at JMS Connector to address vulerabilities for spring-jms lower versions.

W-12950397
## [](#1-8-7)1.8.7 **January 18, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

The JMS Connector Publish operation no longer fails reconnecting on ConnectionFailedException.

W-12302934
## [](#1-8-6)1.8.6 **November 02, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

The JMS Connector Consume operation no longer duplicates messages when the operation stops consuming messages.

W-11786899

The JMS Connector Consume operation now stops correctly when it stops consuming messages.

W-11853709
## [](#1-8-5)1.8.5 **October 31, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

JMS Connector now uses correctly an SSL connection with Active MQ and XA.

W-11786346
## [](#1-8-4)1.8.4 **June 3, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

SessionCacheSize behavior now has impact on the total number of sessions that the connector creates.

W-11056232

Updated spring-jms to version 5.3.20 to address vulnerabilities for lower spring-jms versions.

W-11157710
## [](#1-8-3)1.8.3 **Apr 20, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

Fixed JMS Connector concurrency limitation for the Consume operation.

W-10685928
## [](#1-8-2)1.8.2 **Dec 21, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

Fixed Bitronix errors when a TransactionException occurs.

JMSCLI-26]
## [](#1-8-1)1.8.1 **Nov 4, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

JDK

8
### Fixed Issues
Issue ID

Reconnection did not work when using TLS because SslContext was lost between reconnection attempts.

JMSC-93
## [](#1-8-0)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
Software Version

Mule

4.1.1 and later

JDK

8
## [](#1-7-5)1.7.5 **May 06, 2021** ### [](#fixed-issues-25)Fixed Issues - A thread leaked when connections were validated on Mule runtime. (JMSCLI-20) ## [](#1-7-4)1.7.4 **April 14, 2021** ### [](#fixed-issues-26)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)1.7.3 **January 13, 2021** ### [](#fixed-issues-27)Fixed Issues Fixed a session leak that happened when listening to an inexistent queue. (JMSCLI-12) ## [](#1-7-2)1.7.2 **January 7, 2021** ### [](#fixed-issues-28)Fixed Issues Fixed a reconnection issue that occurred when an exception was thrown while publishing. (JMSCLI-10) ## [](#1-7-1)1.7.1 **August 12, 2020** ### [](#fixed-issues-29)Fixed Issues Fixed a connection leak that occurred when using DataWeave expressions on the connector configuration. (JMSC-70) ## [](#1-7-0)1.7.0 **June 8, 2020** ### [](#features)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)1.6.3 **October 15, 2019** ### [](#known-issues)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-30)Fixed Issues - Fixed a bug that made apps fail to deploy, even when configured with `failsDeployment="false"`. (MULE-17602) ## [](#1-6-2)1.6.2 **August 9, 2019** ### [](#fixed-issues-31)Fixed Issues - JMS Connector now honors payload encoding when publishing message to a JMS queue. (MULE-17286) ## [](#1-6-0)1.6.0 **June 13, 2019** ### [](#features-2)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)1.5.1 **June 12, 2019** ### [](#fixed-issues-32)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)1.5.0 **May 29, 2019** ### [](#features-3)Features - Make XA pool configurable in the JMS connector. (MULE-16926) ### [](#fixed-issues-33)Fixed Issues - JMS Publish Consumer Operation leaks connection. (MULE-16927) ## [](#1-4-1)1.4.1 **May 28, 2019** ### [](#fixed-issues-34)Fixed Issues - Fix issue with reconnection ## [](#1-4-0)1.4.0 **May 27, 2019** ### [](#fixed-issues-35)Fixed Issues - Fix issue with XA transactions on reconnection scenarios. ## [](#1-3-7)1.3.7 **April 17, 2019** ### [](#features-4)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)1.3.6 **April 3, 2019** ### [](#features-5)Features - Fixed a bug that prevented the usage of the connector as a proxy for some brokers. ## [](#1-3-5)1.3.5 **March 19, 2019** ### [](#features-6)Features - Fixed a bug that prevented the reconnection stategy to be triggered in the Publish operation. ## [](#1-3-4)1.3.4 **February 22, 2019** ### [](#features-7)Features - Added a new icon to the connector. - Fixed a bug around JNDI lookup destinations ## [](#1-3-3)1.3.3 **January 14, 2019** ### [](#features-8)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)1.3.2 **November 27, 2018** ### [](#features-9)Features - Fixed a deadlock when using the JMS Listener on too quick flows, which caused listeners to stop receiving messages. ### [](#fixed-issues-36)Fixed Issues - Application hangs after receiving a few messages from ActiveMQ in Mule 4.x. (MULE-16087) ## [](#1-3-1)1.3.1 **Deprecated** **October 29, 2018** ### [](#features-10)Features - Fixed issue that prevent the usage of a TLS Context. ### [](#fixed-issues-37)Fixed Issues - JMS Connector doesn’t initialize the TLS Context if it is defined as a child element. (MULE-15930) ## [](#1-3-0)1.3.0 **Deprecated** **August 29, 2018** ### [](#features-11)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-38)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)1.2.3 **August 7, 2018** ### [](#fixed-issues-39)Fixed Issues - Fixed issue that prevented receiving messages published through the Artemis Management Console. (MULE-15431) ## [](#1-2-2)1.2.2 **May 7, 2018** ### [](#features-12)Features Minor internal upgrades. ### [](#fixed-issues-40)Fixed Issues - Update Spring JMS to version 5.0.5.RELEASE. (MULE-14966) - Upgrade Jackson to 2.9.5. (MULE-14795) ## [](#1-2-1)1.2.1 **April 11, 2018** ### [](#features-13)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-41)Fixed Issues - JMS Publish Consume operation throws JmsIllegalBodyException when returning ManagedCursorStreamProvider in the payload. (MULE-14852) ## [](#1-2-0)1.2.0 **Mar 26, 2018** ### [](#features-14)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)Upgrade Requirements Mule 4.1.1 ### [](#fixed-issues-42)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)1.1.0 **January 19, 2018** ### [](#features-15)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-2)Upgrade Requirements Mule 4.1 ### [](#fixed-issues-43)Fixed Issues - JMS Config - ActiveMQ label incorrectly displayed. (MULE-14105) ## [](#see-also)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)