Chapter 3. JMS Transactions

download PDF


JMS endpoints create special problems when transactions are enabled. Their behavior is effected by the type of transaction manager in use, the caching level in use, and the message exchange pattern in use.

3.1. Configuring the JMS Component


To enable transactions in a JMS component (thus enabling JMS endpoints to play the role either of a transactional resource or a transactional client), you need to:
  • set the transacted property
  • provide the JMS component with a reference to a suitable transaction manager
In addition, you may want to adjust the JMS component's cache level setting. External transaction managers can impact caching performance.

Camel JMS component configuration

The easiest way to configure a JMS endpoint to participate in transactions is to create a new an instance of a Camel JMS component that has the proper settings. To do so:
  1. Create a bean element that has its class attribute set to org.apache.camel.component.jms.JmsComponent.
    This bean creates an instance of the JMS component.
  2. Set the bean's id attribute to a unique, short, string.
    The id will be used to create route endpoint's that use this JMS component.
  3. Add an empty property child to the bean.
  4. Add a name attribute with the value of configuration to the property element.
  5. Add a ref attribute whose value is the id of a JmsConfiguration bean to the property element.
    The JmsConfiguration bean is used to configure the JMS component.
  6. Create a bean element that has its class attribute set to org.apache.camel.component.jms.JmsConfiguration.
    This bean creates an instance of the JMS component configuration.
  7. Set the bean's id attribute to the value supplied for the ref attribute in Step 5.
  8. Add a property child to the bean to configure the JMS connection factory.
    1. Set the name attribute to connectionFactory.
    2. Set the ref attribute to the id of a bean that configures a JMS connection factory.
  9. Add an empty property child to the bean that specifies the transaction manager the component will use.
    1. Set the name attribute to transactionManager.
    2. Set the ref attribute to the id of a bean that configures transaction manager the endpoint will use.
  10. Add an empty property child to the bean that configures the component to participate in transactions.
    1. Set the name attribute to transacted.
    2. Set the value attribute to true.
      The transacted property determines if the endpoint can participate in transactions.
  11. Optionally add an empty property child to the bean to change the default cache level.
    1. Set the name attribute to cacheLevelName.
    2. Set the value attribute to to a valid cache level. For example, the recommended cache level for an ActiveMQ messaging resource is CACHE_CONSUMER, which gives optimum performance. For more details, see the section called “Cache levels and performance”.
The JmsComponent bean's id specifies the URI prefix used by JMS endpoints that will use the transactional JMS component. For example, in Example 3.1, “JMS Transaction Manager Configuration” the JmsComponent bean's id equals jmstx, so endpoint that use the configured JMS component use the jmstx: prefix.
The JmsConfiguration class supports a large number of other properties, which are essentially identical to the JMS URI options described in .

Cache levels and performance

The settings for JMS cache level can impact performance when you are using transactions. The default cache level is CACHE_AUTO. This default auto detects if an external transaction manager is in use and sets the cache level as follows:
  • CACHE_CONSUMER if only local JMS resources are in use
  • CACHE_NONE if an external transaction manager is in use
This behavior guarantees that there will not be any conflicts between caching and the transaction manager because some XA transaction managers require that caching is disabled. However, this behavior may not produce optimal performance.
If your transaction manager does not require that caching be disabled, you can raise the cache level to improve performance. Consult your transaction manager's documentation to determine what caching level it can support. Then override the default cache level by setting the JMS component's cacheLevelName property to the new cache level.
When the transactional resource is ActiveMQ, it is generally safe to set the cache level to CACHE_CONSUMER and this setting is recommended, because it improves performance significantly.
See for information on setting the cache level of the JMS component.


Example 3.1, “JMS Transaction Manager Configuration” shows the configuration of a JMS component, jmstx that supports Spring transactions. The JMS component is layered over an embedded instance of Apache ActiveMQ and the transaction manager is an instance of JmsTransactionManager.

Example 3.1. JMS Transaction Manager Configuration

<beans xmlns="" 
  <bean id="jmstx" class="org.apache.camel.component.jms.JmsComponent"> 
    <property name="configuration" ref="jmsConfig" /> 

  <bean id="jmsConfig" class="org.apache.camel.component.jms.JmsConfiguration"> 
      <property name="connectionFactory" ref="jmsConnectionFactory"/> 
      <property name="transactionManager" ref="jmsTransactionManager"/> 
      <property name="transacted" value="true"/>
      <property name="cacheLevelName" value="CACHE_CONNECTION"/>

  <bean id="jmsTransactionManager" class="org.springframework.jms.connection.JmsTransactionManager">
    <property name="connectionFactory" ref="jmsConnectionFactory" />
  <bean id="jmsConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
    <property name="brokerURL" value="vm://broker1?brokerConfig=xbean:tutorial/activemq.xml"/>

To use this JMS component in a route you would use the URI prefix jmstx: as shown in Example 3.2, “URI for Using Transacted JMS Endpoint”.

Example 3.2. URI for Using Transacted JMS Endpoint

Red Hat logoGithubRedditYoutubeTwitter


Try, buy, & sell


About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.