Chapter 1. Overview

AMQ JMS is a Java Message Service (JMS) 2.0 client for use in messaging applications that send and receive AMQP messages.

AMQ JMS is part of AMQ Clients, a suite of messaging libraries supporting multiple languages and platforms. For an overview of the clients, see AMQ Clients Overview. For information about this release, see AMQ Clients 2.3 Release Notes.

AMQ JMS is based on the JMS client from Apache Qpid.

1.1. Key features

  • JMS 1.1 and 2.0 compatible
  • SSL/TLS for secure communication
  • Flexible SASL authentication
  • Automatic reconnect and failover
  • Ready for use with OSGi containers
  • Pure-Java implementation

AMQ JMS does not currently support distributed transactions (XA). If your application requires distributed transactions, it is recommended that you use the AMQ Core Protocol JMS client.

1.2. Supported standards and protocols

AMQ JMS supports the following industry-recognized standards and network protocols:

1.3. Supported configurations

AMQ JMS supports the following OS and language versions:

  • Red Hat Enterprise Linux 6 and 7 with the following JDKs

    • OpenJDK 8
    • Oracle JDK 8
    • IBM JDK 8
  • HP-UX 11i with HP-UX JVM 8
  • IBM AIX 7.1 with IBM JDK 8
  • Oracle Solaris 10 and 11 with Oracle JDK 8
  • Microsoft Windows Server 2012 R2 with Oracle JDK 8

For more information, see Red Hat AMQ 7 Supported Configurations.

1.4. Terms and concepts

This section introduces the core API entities and describes how they operate together.

Table 1.1. API terms



An entry point for creating connections


A channel for communication between two peers on a network


A context for producing and consuming messages


A channel for sending messages to a destination


A channel for receiving messages from a destination


A named location for messages, either a queue or a topic


A stored sequence of messages


A stored sequence of messages for multicast distribution


A mutable holder of application data

AMQ JMS sends and receives messages. Messages are transferred between connected peers using message producers and consumers. Producers and consumers are established over sessions. Sessions are established over connections. Connections are created by connection factories.

A sending peer creates a producer to send messages. The producer has a destination that identifies a target queue or topic at the remote peer. A receiving peer creates a consumer to receive messages. Like the producer, the consumer has a destination that identifies a source queue or topic at the remote peer.

A destination is either a queue or a topic. In JMS, queues and topics are client-side representations of named broker entities that hold messages.

A queue implements point-to-point semantics. Each message is seen by only one consumer, and the message is removed from the queue after it is read. A topic implements publish-subscribe semantics. Each message is seen by multiple consumers, and the message remains available to other consumers after it is read.

See the JMS tutorial for more information.

1.5. Document conventions

This document uses the following conventions for the sudo command and file paths.

The sudo command

In this document, sudo is used for any command that requires root privileges. You should always exercise caution when using sudo, as any changes can affect the entire system.

For more information about using sudo, see The sudo Command.

About the use of file paths in this document

In this document, all file paths are valid for Linux, UNIX, and similar operating systems (for example, /home/...). If you are using Microsoft Windows, you should use the equivalent Microsoft Windows paths (for example, C:\Users\...).