--- schema_version: "1" id: 04b485a6ee7c729325a77a0c6568098baa7b67e774cce0193221d76f95cd408c title: IBM MQ Connector Release Notes collection: mulesoft version: current locale: ja-jp portal_url: https://docs.salesforce.com/mulesoft/current/ja-jp/release-notes/connector/connector-ibm-mq.md canonical_url: https://docs.mulesoft.com/jp/release-notes/connector/connector-ibm-mq source_site: docs.mulesoft.com content_type: documentation content_hash: 939ae29c259fcc9926cb060c0a002c9fdf9fe0508754bece357dc0cc16116273 description: MuleSoft Documentation Site latest: true --- # IBM MQ 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 IBM MQ (IBM MQ Connector) enables an app to do messaging to a IBM MQ Broker using the IBM MQ JMS implementation. Guide: [IBM MQ Connector User Guide](https://docs.mulesoft.com/ibm-mq-connector/latest/) ## [](#2-0-1)2.0.1 **October 13, 2026** ### Compatibility
Software Version

Mule

4.10 and later

OpenJDK

17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

JMSCC0111 errors no longer occur when a Client ID is configured and connection caching is enabled for the IBM MQ Connection or the IBM MQ XA Connection. The client ID is now applied to the cached connection only, instead of the cached connection and the IBM MQ connection factory.

W-14100275

Publishing to a full queue now raises an IBM-MQ:PUBLISHING error for MQRC_Q_FULL (2053), instead of treating the error as a lost connection and reconnecting, when the app uses the legacy IBM MQ client library (com.ibm.mq.allclient).

W-24012864

These libraries are upgraded to address reported security vulnerabilities:

  • The Spring Framework libraries spring-jms, spring-core, spring-beans, spring-context, spring-expression, and spring-messaging are upgraded to version 6.2.19.

  • The slf4j-api and jcl-over-slf4j libraries are upgraded to version 2.0.20.

  • The commons-codec library is upgraded to version 1.22.1.

  • The guava library is upgraded to version 33.7.2-jre.

  • The c3p0 library is upgraded to version 0.14.2.

  • The mchange-commons-java library is upgraded to version 0.6.0.

  • The ActiveMQ client library is upgraded to version 6.3.2.

W-24311628, W-24012864, W-24137088
## [](#2-0-0)2.0.0 **August 3, 2026** ### What’s New - This connector is now compatible with Java 17 only. - This connector uses the Jakarta Messaging (`jakarta.jms`) namespace, instead of `javax.jms`. The recommended IBM MQ client library is now `com.ibm.mq.jakarta.client` 9.4.5.1, instead of `com.ibm.mq.allclient`. If your app supplies the `com.ibm.mq.allclient` library, the connector wraps it to expose a `jakarta.jms` connection factory for backward compatibility only. See [Support for the Legacy javax.jms Client Library](https://docs.mulesoft.com/ibm-mq-connector/latest/#javax-client-library). - The `enableXa` attribute is removed from the connection configuration. - The connector provides separate connection types for XA and non-XA transactions. You can now select the new **IBM MQ XA Connection** type in the **IBM MQ Config** window. This new connection type replaces the previous `enableXa` attribute on a single connection. The existing **IBM MQ Connection** type is now used only for non-XA scenarios. See [Handling Transactions in IBM MQ](https://docs.mulesoft.com/ibm-mq-connector/latest/ibm-mq-transactions). - The connection element is renamed from `` to ``. Apps that use the previous element name or the `enableXa` attribute don’t start until you update the configuration. See [Upgrading and Migrating IBM MQ Connector to Version 2.x](https://docs.mulesoft.com/ibm-mq-connector/latest/ibm-mq-connector-upgrade-migrate). - The **XA connection pool** configuration (**Min Pool Size**, **Max Pool Size**, and **Max Idle Seconds**) applies only to the **IBM MQ XA Connection** type. ### Compatibility
Software Version

Mule

4.10 and later

OpenJDK

17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### 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 IBM MQ client library is upgraded to com.ibm.mq.jakarta.client version 9.4.5.1.

  • The Spring framework is upgraded to version 6.2.19.

  • The Mule JMS client library is upgraded to version 2.0.1.

W-21756343
## [](#1-9-0)1.9.0 **June 15, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

The On New Message source no longer leaks inactivity monitoring threads during reconnection cycles. The connector now cancels stale monitoring tasks before starting new ones, preventing thread accumulation and high resource usage.

W-22394423

The connector now logs NullPointerException errors that occur during message listener teardown as WARN instead of ERROR. This prevents unnecessary operator escalations for exceptions that do not impact application functionality.

W-21191825
## [](#1-8-3)1.8.3 **May 8, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

These libraries are upgraded to address reported security vulnerabilities:

  • The grizzly-http, grizzly-http-server, grizzly-framework, grizzly-websockets, and grizzly-connection-pool libraries are upgraded to version 2.4.4.

  • The grizzly-http-client library is upgraded to version 1.16.

  • The quartz library is upgraded to version 2.3.2.

  • The c3p0 library is upgraded to version 0.10.2.

  • The mchange-commons-java library is upgraded to version 0.3.2.

  • The guava library is upgraded to version 33.4.8-jre.

  • The commons-io library is upgraded to version 2.18.0.

  • The commons-text library is upgraded to version 1.14.0.

  • The commons-lang3 library is upgraded to version 3.18.0.

  • The javax.mail library is upgraded to version 1.4.7.

W-22376257
## [](#1-8-2)1.8.2 **April 13, 2026** ### What’s New - The connector now supports Automatic Application Balancing in IBM MQ Uniform Clusters with the new **Client Reconnect Options** and **Client Reconnect Timeout** fields. When configured with a Connection Name List or CCDT, the connector enables dynamic client connection rebalancing across Queue Managers, allowing applications to automatically reconnect to available queue managers in the cluster. See [IBM MQ Connector Reference - Client](https://docs.mulesoft.com/ibm-mq-connector/latest/ibm-mq-xml-ref#client). ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

The Publish operation no longer treats queue-full errors as connection errors, which previously caused unnecessary connection resets and flow hangs. The connector now throws the IBM-MQ:PUBLISHING error for queue-full conditions, enabling reliable error handling without disrupting the connection.

W-20427004
## [](#1-8-1)1.8.1 **January 24, 2026** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

The On New Message source now supports the Inactivity Timeout Minutes field, which allows the source to reconnect automatically if no message is received within the specified period. The default value is 0.

W-20609348

The commons-lang3 dependency is upgraded to version 3.18.0 to address CVE-2025-48924.

W-21054728

MQRC_DATA_LENGTH_ERROR (2010) is now treated as non-recoverable, so the connector stops retrying and surfaces the terminal validation failure.

W-18834134

IBM MQ Connector now converts MQJMS2007 errors to ConnectionException so the Publish and Publish consume operations reconnect automatically.

W-20527836
## [](#1-8-0)1.8.0 **December 3, 2025** ### What’s New - This connector now supports TLS 1.3 cipher suites as defined in RFC 8446, enabling secure channel negotiation using modern cryptographic protocols. Both IBM and Oracle JDKs implement TLS 1.3 cipher suites using standardized names, providing a unified configuration model across different runtime environments. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

9.2.x and later (for full TLS 1.3 support)
### Fixed Issues
Issue Resolution ID

MUnit tests no longer fail with HTTP 404 errors when deleting queues via the IBM MQ REST API while using the Netty HTTP service. Tests now properly stop listener flows and wait for connection cleanup to complete before proceeding with queue deletion.

W-20083097
## [](#1-7-8)1.7.8 **September 17, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The Publish operation now supports the ADMIN.QUEUE destination, which allows you to refresh the connection or reconnect listeners at runtime. This is useful for maintenance or error recovery without stopping the Mule application. For more information, see Configure ADMIN.QUEUE to Refresh Connections.

W-17295817, W-18756149, W-19024281
## [](#1-7-7)1.7.7 **July 15, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

In IBM MQ 1.7.4, memory leak issues were resolved for Mule runtime versions running on Java 8. However, Mule runtime versions running on Java 11 or 17 used reflection, which caused IllegalAccessException errors. These are resolved now, and the connector no longer experiences memory leaks or reflection-related errors on Java 11 or 17.

W-18591182
## [](#1-7-6)1.7.6 **May 28, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The mule-jms-client dependency is upgraded to 1.13.24.

W-17156082

Reconnection issues no longer occur when you use a connection list with the connector.

W-17156082

Reconnection issues no longer occur when you use the Publish Consume operation.

W-17780005

Memory leaks no longer occur in JmsListener.

W-17967138
## [](#1-7-5)1.7.5 **March 21, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

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

W-17968742
## [](#1-7-4)1.7.4 **March 3, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

A NullPointerException error no longer occurs when stopping the JMS connection resource.

W-16504615

There are no longer memory leaks caused by the Thread Context Class Loader (TCCL) of the JMSCCThreadPoolMaster ThreadGroup.

W-13521498, W-13521848
## [](#1-7-3)1.7.3 **February 21, 2025** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

IBM MQ Connector now automatically attempts to reconnect for the Publish, Publish consume, and Consume operations after a connection is lost.

W-15854054, W-17584793
## [](#1-7-2)1.7.2 **November 14, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The org.apache.commons:commons-lang3 library is upgraded to version 3.17.0.

W-17024625

The org.apache.commons:commons-io library is upgraded to version 2.17.0.

W-17024625
## [](#1-7-1)1.7.1 **August 15, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The connector now attempts to reconnect when the JMSWMQ0018 error occurs in the Publish operation.

W-15829872

The connector now throws all JMSException errors in the Publish operation.

W-16146401
## [](#1-7-0)1.7.0 **April 18, 2024** ### What’s New - This connector is now FIPS 140-2 compliant. ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
## [](#1-6-24)1.6.24 **March 19, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The IBM MQ Connector no longer fails with NoSuchFieldException when an XA transaction exception occurs.

W-12099940
## [](#1-6-23)1.6.23 **January 30, 2024** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8, 11, and 17

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The IBM MQ Connector now attempts to reconnect when MQRC_HOST_NOT_AVAILABLE or MQRC_CONNECTION_BROKEN errors occur.

W-14451111
## [](#1-6-22)1.6.22 **January 5, 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

IBM MQ

8 and 9
## [](#1-6-21)1.6.21 **November 7, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The IBM MQ Connector no longer fails when the application is redeployed within a domain connection. The runtime version configuration must be upgraded to 4.3.0-20231026 or 4.4.0-20231026 or later.

W-12388528
## [](#1-6-20)1.6.20 **August 10, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

Bumped org.springframework:spring-jms to version 5.3.29 to address security vulnerabilities.

W-13830571

Bumped commons-io:commons-io to version 2.13.0 to address security vulnerabilities.

W-13830571

Bumped org.apache.commons:commons-lang3 to version 3.13.0 to address security vulnerabilities.

W-13830571

Bumped io.qameta.allure:allure-junit4 to version 2.23.0 to address security vulnerabilities.

W-13830571

Bumped org.apache.maven.plugins:maven-surefire-plugin to version 3.1.2 to address security vulnerabilities.

W-13830571
## [](#1-6-19)1.6.19 **April 05, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

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

W-12950397
## [](#1-6-18)1.6.18 **March 23, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The IBM MQ Connector now avoids thread leaks on disconnections.

W-12350716
## [](#1-6-17)1.6.17 **January 19, 2023** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue Resolution ID

The IBM MQ Connector Publish operation no longer fails when a connectivity error occurs.

W-12189382
## [](#1-6-16)1.6.16 **November 4, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

IBM MQ Connector now avoids thread leaks in the IBM driver thread workers.

W-12003685
## [](#1-6-15)1.6.15 **October 6, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

Update of dependencies.

W-11861100
## [](#1-6-14)1.6.14 **September 29, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

IBM MQ Connector no longer gets stuck when stopping a source that was processing messsages.

W-11476953
## [](#1-6-13)1.6.13 **July 7, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

The CCSID property of the connection provider now works correctly when configured.

W-10583435

Intermittent IBM MQ messages no longer error out with unprintable characters shown in messages written to the backout queue.

W-11337787
## [](#1-6-12)1.6.12 **June 29, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

Updated visually in Anypoint Studio CSS ID field to CCS ID.

W-11267520
## [](#1-6-11)1.6.11 **June 8, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

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

W-11157721
## [](#1-6-10)1.6.10 **Jan 27, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

Fixed internal tests.

IMC-53
## [](#1-6-9)1.6.9 **Jan 20, 2022** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

Fixed Bitronix errors when a TransactionException occurs.

JMSCLI-26
## [](#1-6-8)1.6.8 **October 26, 2021** ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### Fixed Issues
Issue ID

Fixed a source reconnection issue when working with XA transactions.

IMC-97
## [](#1-6-7)1.6.7 **August 20, 2021** ### What’s New - Optimized the connector to improve its overall stability and performance. (IMC-93) ### Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
## [](#1-6-6)1.6.6 **May 6, 2021** ### [](#compatibility-35)Compatibility
Software Version

Mule

4.1.1 and later

OpenJDK

8 and 11

IBM MQ

8 and 9
### [](#fixed-issues-32)Fixed Issues - A thread leaked when connections were validated on Mule runtime. (JMSCLI-20) - Connections did not recover when the Broker Queue Manager was restarted while publishing, in the context of an XA transaction. (JMSCLI-21) ## [](#1-6-5)1.6.5 **April 21, 2021** ### [](#fixed-issues-33)Fixed Issues - IBM MQ Connector did not forward messages to the configured backout or dead letter queue when the message processing failed during the XA transaction (JMSCLI-19). ## [](#1-6-4)1.6.4 **March 1, 2021** ### [](#fixed-issues-34)Fixed Issues - Fixed an issue that generated contention and affected the concurrency in the Publish Consume operation (JMSCLI-14). ## [](#1-6-3)1.6.3 **November 17, 2020** ### [](#fixed-issues-35)Fixed Issues - Fixed an issue that blocked listener threads when calling the recover-session twice (JMSCLI-9). ## [](#1-6-2)1.6.2 **October 21, 2020** ### [](#fixed-issues-36)Fixed Issues - Fixed an issue in which IBM MQ Connector caused a connection leak when using dynamic configurations (IMC-73). - Added a timeout verification to prevent connections from hanging indefinitely (JMSCLI-6). ## [](#1-6-1)1.6.1 **June 16, 2020** ### [](#fixed-issues-37)Fixed Issues Deadlock on stopping apps with on flight messages in WMQ listeners. (IMC-70) ## [](#1-6-0)1.6.0 **June 5, 2020** ### [](#new-features)New Features Added support to avoid automatic reply when the inbound message contains a ReplyTo header. (IMC-68) ## [](#1-5-9)1.5.9 **May 4, 2020** ### [](#fixed-issues-38)Fixed Issues Fixed issue that caused sessions to fail to close in cases where the listener was set to a nonexistent queue. (MULE-18377) ## [](#1-5-8)1.5.8 **May 4, 2020** ### [](#fixed-issues-39)Fixed Issues Fixed issue that caused IBM MQ Connector to trigger a `MULE:UNKNOWN` error instead of `IBM-MQ:PUBLISHING` (EE-7323). ## [](#1-5-7)1.5.7 **April 13, 2020** ### [](#fixed-issues-40)Fixed Issues Fixed issue that caused IBM MQ Connector to fail to reconnect to all queues after stopping and starting the channel (EE-7282). ## [](#1-5-6)1.5.6 **March 30, 2020** ### [](#fixed-issues-41)Fixed Issues IBM MQ uses the JMS API to get the correlation ID in the publish-consume operation (EE-7270). ## [](#1-5-5)1.5.5 **February 28, 2020** ### [](#fixed-issues-42)Fixed Issues Made changes so that IBM MQ operations should be blocking due to requirements in the IBM MQ driver (EE-7235). IBM MQ driver does not reestablish connections correctly (EE-7253). ## [](#1-5-4)1.5.4 **February 12, 2020** ### [](#fixed-issues-43)Fixed Issues The issue that caused mishandling of the correlation ID in MQ with a non JMS compliant target client in a publish-consume operation is fixed (EE-7214). ## [](#1-5-3)1.5.3 **November 27, 2019** ### [](#fixed-issues-44)Fixed Issues The issue where reconnection failed after stopping and restarting the Server Connection Channel is fixed (EE-7253). ## [](#1-5-2)1.5.2 **October 1, 2019** ### [](#fixed-issues-45)Fixed Issues - IBM MQ Connector fails to recover after connection error. - IBM MQ Connector is retrying with old session, which resulted in message loss when the message was sent with a `Reply To` header. - Upgrade mule-extensions-patent, mule-core-modules-parent, and mule-ee-core-modules-parent to 1.1.6 (MULE-17121). ## [](#1-5-1)1.5.1 **June 25, 2019** ### [](#fixed-issues-46)Fixed Issues IBM MQ messages are going into uncommitted state. ## [](#1-5-0)1.5.0 **June 13, 2019** ### [](#new-features-2)New Features Added support for different [request reply patterns](https://docs.mulesoft.com/ibm-mq-connector/latest/ibm-mq-publish-consume) for the **Publish Consume** and **Listener** operations. ## [](#1-4-1)1.4.1 **June 12, 2019** ### [](#fixed-issues-47)Fixed Issues - The Consume operation didn’t roll back correctly on XA transactions. (MULE-16969) - Bridge scenario with XA hangs in some cases. ## [](#1-4-0)1.4.0 **May 29, 2019** ### [](#new-features-3)New Features - Make XA Connection pool configurable. - Fixed issue with Publish Consume Operation leaking connections. ## [](#1-3-0)1.3.0 **May 27, 2019** ### [](#new-features-4)New Features Fixed issue with XA transactions on reconnection scenarios. ## [](#1-2-6)1.2.6 **April 30, 2019** ### [](#new-features-5)New Features Fixed reconnection issues when using session caching. ## [](#1-2-5)1.2.5 **April 26, 2019** ### [](#new-features-6)New Features - Connector now implements its own reconnection logic. - Custom way of cleaning consumer’s listeners. ## [](#1-2-4)1.2.4 **April 4, 2019** ### [](#new-features-7)New Features Clean up the IBM MQ exception listener states so that they are now done silently. ## [](#1-2-3)1.2.3 **March 29, 2019** ### [](#new-features-8)New Features - Fixed reconnection issue when Queue Manager is shutdown while handling REPLY\_TO. - Fixed IBM MQ Client unhandled exception when cleaning a consumer’s message listener. - Cleanup of IBM MQ exception listener state, when a cached connection is not cleaned up. ## [](#1-2-2)1.2.2 **March 19, 2019** ### [](#new-features-9)New Features Fixed a bug that prevented the reconnection strategy to be triggered in the publish operation. ## [](#1-2-1)1.2.1 **February 22, 2019** ### [](#new-features-10)New Features Fixed a bug with the MQ Listener using Transactional Action Begin that stopped messages from being processed. ## [](#1-2-0)1.2.0 **February 5, 2019** ### [](#new-features-11)New Features Out of the box support for TLS/SSL configurations. ## [](#1-1-2)1.1.2 **January 14, 2019** ### [](#new-features-12)New Features Fixed connection leaks. These leaks could happen when a Publish action failed internally or when doing an automatic ReplyTo when using the "On New Message" source. ## [](#1-1-1)1.1.1 **November 7, 2018** ### [](#new-features-13)New Features Fixed issue that prevented the connector from setting a Client ID, required for durable subscriptions. ### [](#fixed-issues-48)Fixed Issues Unable to set the Client ID on an IBM MQ Connection. ## [](#1-1-0)1.1.0 **October 26, 2018** ### [](#new-features-14)New Features - Fixed issue that prevented correct execution when using XA Transactions. - Message Listener can be configured to propagate the correlation ID when doing a reply. ### [](#fixed-issues-49)Fixed Issues XA Transaction is not working for IBM MQ Connector. ## [](#1-0-0)1.0.0 **June 29, 2018** ### [](#features-and-enhancements)Features and Enhancements Release of IBM MQ Connector, which supports consuming and publishing messages through the JMS API. ### [](#mule-version)Mule Version Mule 4.1.1 ## [](#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)