JMS changelog

Changelog

2026-07 (Version 14, Current)

• 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.