JVM since1.0.0 Native since1.0.0

Sent and receive messages to/from a JMS Queue or Topic.

What’s inside

Please refer to the above link for usage and configuration details.

Maven coordinates

Or add the coordinates to your existing project:


Check the User guide for more information about writing Camel Quarkus applications.


Message mapping with org.w3c.dom.Node

The Camel JMS component supports message mapping between jakarta.jms.Message and org.apache.camel.Message. When wanting to convert a Camel message body type of org.w3c.dom.Node, you must ensure that the camel-quarkus-xml-jaxp extension is present on the classpath.

Native mode support for jakarta.jms.ObjectMessage

When sending JMS message payloads as jakarta.jms.ObjectMessage, you must annotate the relevant classes to be registered for serialization with @RegisterForReflection(serialization = true). Note that this extension automatically sets quarkus.camel.native.reflection.serialization-enabled = true for you. Refer to the native mode user guide for more information.

Support for Connection pooling and X/Open XA distributed transactions

You can use the quarkus-pooled-jms extension to get pooling and XA support for JMS connections. Refer to the quarkus-pooled-jms extension documentation for more information. Currently, it can work with quarkus-artemis-jms, quarkus-qpid-jms and ibmmq-client. Just add the dependency to your pom.xml:


Pooling is enabled by default.

clientID and durableSubscriptionName are not supported in pooling connections. If setClientID is called on a reused connection from the pool, an IllegalStateException will be thrown. You will get some error messages such like Cause: setClientID can only be called directly after the connection is created

To enable XA, you need to add quarkus-narayana-jta extension:


and add the following configuration to your


XA support is only available with quarkus-artemis-jms and ibmmq-client. Also We highly recommend to enable transaction recovery.

Since there is no quarkus extension for ibmmq-client currently, you need to create a custom ConnectionFactory and wrap it by yourself. Here is an example:

public ConnectionFactory createXAConnectionFactory(PooledJmsWrapper wrapper) {
    MQXAConnectionFactory mq = new MQXAConnectionFactory();
    try {
        mq.setHostName(ConfigProvider.getConfig().getValue("", String.class));
        mq.setPort(ConfigProvider.getConfig().getValue("", Integer.class));
        mq.setChannel(ConfigProvider.getConfig().getValue("", String.class));
        mq.setQueueManager(ConfigProvider.getConfig().getValue("", String.class));
            ConfigProvider.getConfig().getValue("", String.class));
            ConfigProvider.getConfig().getValue("", String.class));
    } catch (Exception e) {
        throw new RuntimeException("Unable to create new IBM MQ connection factory", e);
    return wrapper.wrapConnectionFactory(mq);

If you use ibmmq-client to consume messages and enable XA, you need to configure TransactionManager in the camel route like this:

TransactionManager transactionManager;

public void configure() throws Exception {

public PlatformTransactionManager getTransactionManager() {
    return new JtaTransactionManager(transactionManager);

Otherwise, you will get an exception like MQRC_SYNCPOINT_NOT_AVAILABLE.

transferException option in native mode

To use the transferException option in native mode, you must enable support for object serialization. Refer to the native mode user guide for more information.

You will also need to enable serialization for the exception classes that you intend to serialize. For example.

@RegisterForReflection(targets = { IllegalStateException.class, MyCustomException.class }, serialization = true)