JMS Connector Release Notes - Mule 4

Support Category: Select

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.

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

Anypoint Studio

7.1.1 and later

JDK

8

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. (JMSC-12)

1.7.2

January 7, 2021

Fixed Issues

Fixed a reconnection issue that occurred when an exception was thrown while publishing. (JMSC-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

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)

Was this article helpful?

💙 Thanks for your feedback!