Skip to main content
Feedback

JMS changelog

Updated 

Changelog

2026-11 (Version 19, Runtime release)

  • For the Send action, fixed an issue where the tracking field values were not populated at the document level on the Process Reporting page.

This fix is not in the runtime release.

  • For Websphere MQ, whenever a query parameter is passed along with Queue/Topic, the system truncated the queue:// or topic:// value from the destination name, which caused an error.

  • Resolved an issue where sending a message to a Dynamic Destination profile with JMS and Oracle AQ resulted in an error.

These fixes are in the runtime release.

2026-09 (Version 17, Current)

  • Resolved an issue where JMS connector operations using the Listen action that were created before the September 2026 release could not be edited or saved and incorrectly displayed a banner stating the action was no longer available. For JMSv2 (Early Access) trading partner communications, Listen is no longer offered as a trading partner action.

2026-09 (Version 16)

  • Added the broker-provided JMSXDeliveryCount as an integer Document Property on Get and Listen operations. The value starts at 1 and increments with each redelivery; it is omitted when the broker does not provide it and is not available on Send operations.

  • Resolved critical and high severity Snyk vulnerabilities by upgrading jackson-databind to version 2.18.9.

  • Resolved an issue where messages sent using JMS (Legacy) with custom properties that have no assigned value were incorrectly converted into a literal "null" string. Now, custom properies with a null value remain a null value when retrieved by JMS.

  • Resolved an issue where after the execution of JMS GET and SEND operations, the system was not assigning Status Code and Status Message values.

2026-07 (Version 14)

  • Connector name has been changed from JMS V2 to JMS.

  • Updated the JMS connector to support dynamic status reporting for the Listen operation.

  • Fixed an issue where setting Pool Maximum Connections to 0 (unlimited) was not honored by the connector.

  • Fixed a connection pool corruption issue where a failed connection initialization could add an invalid entity to the pool, corrupting the active connection count.

  • Fixed incorrect help text for Pool Maximum Idle Time and Pool Maximum Wait Time, which indicated seconds but the connector expected milliseconds.

2026-05 (Version 11)

  • Enhanced the JMS v2 connector to reduce excessive log noise in container logs when processing JSON payloads in Get and Listen operations, improving log readability and troubleshooting efficiency.

2026-01 (Version 10)

  • The JMS V2 Listener now automatically retries lost connections up to six times at progressive intervals (immediately, then at 10s, 30s, 60s, 120s, and 300s) before requiring a manual restart, aligning its connection resilience behavior with JMS V1.

2025-09 (Version 9)

  • Updated the JMS V2 connector to set the message priority as per the operation property or dynamic operation property value, enabling users to send messages with the desired priority.

  • Introduced a new Client ID field in the GET, SEND, and LISTEN operations of the JMS V2 connector, enabling users to execute multiple processes concurrently using the same connection.

2024-11 (Version 8)

  • JMS V2 Connector of server type Websphere MQ no longer fails with a NullPointerException when it tries to get messages from Websphere MQ, which are sent through the external application or created within the Websphere MQ console.

2024-04 (Version 7)

  • The GET, SEND, and LISTEN operations now support IBM Websphere MQ.

  • You can now test your connection with an IBM Websphere server type.

2022-11 (Version 1)

  • The JMS V2 connector is generally available (GA) to all customers with this release.
On this Page