ActiveMQ Classic Jakarta Messaging 3.1 & JMS 2.0 Support

ActiveMQ Classic 5.x & 6.x support for Jakarta Messaging 3.1 & JMS 2.0 is in progress. If you need full support for Jakarta Messaging 3.1 or JMS 2.0 we recommend ActiveMQ Artemis.

Transition Approach

Initially, ActiveMQ Classic clients will not support all JMS 2.0 functionality and will throw an UnsupportedOperationException (RuntimeException) for unsupported methods and features, such as those for async send with a CompletionListener, sending messages with a delivery delay, and using shared topic consumers.

As features are implemented in subsequent releases, these exceptions will be replaced with fully functional methods, examples and unit tests. See later/below for more details on implementation progress.

Jakarta Messaging

Support for JMS 2.0 also enables building upon this for transition to Jakarta Messaging 3.1 and its new jakarta.jms API namespace rather than the historical javax.jms namespace.

• The standard for Java Enterprise features going forward
• Required for Spring 6
• Required for Jakarta EE 9 + 10.
• JMS API Java package name-change only
• ActiveMQ Classic package names do not change

This allows for a dependency-update-only approach to the transition without having to re-code going forward!

There is no functional change, this is purely a Java package naming change:

import javax.jms.ConnectionFactory
import javax.jms.Message
import javax.jms...

Becomes:

import jakarta.jms.ConnectionFactory
import jakarta.jms.Message
import jakarta.jms...

To use the Jakarta transition client available with ActiveMQ Classic 5.18.x in Maven:

<dependency>
  <groupId>org.apache.activemq</groupId>
  <artifactId>activemq-client-jakarta</artifactId>
  <version>${activemq.version}</version>
</dependency>

Note: With ActiveMQ Classic 6.x the activemq-client-jakarta module is removed as it is no longer needed.

Spring bean usage

Spring bean definitions do not change for Jakarta support.

<bean class="org.apache.activemq.ActiveMQConnectionFactory">

Implementation Progress

The implementation approach is subject to change. Be sure to verify features in release notes.

User feedback is welcome! Please comment on the JIRAs with questions and comments.

Feature notes