Chapter 1. Overview
AMQ JMS Pool is a library that provides caching of JMS connections, sessions, and message producers. It enables reuse of connection resources beyond the standard lifecycle defined by the JMS API.
AMQ JMS Pool operates as a standard JMS
ConnectionFactory instance that wraps the
ConnectionFactory of your chosen JMS provider and manages the lifetime of
Connection objects from that provider based on the configuration of the JMS pool. It can be configured to share one or more connections among callers to the pool
AMQ JMS Pool 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.10 Release Notes.
AMQ JMS Pool is based on the Pooled JMS messaging library.
1.1. Key features
- JMS 1.1 and 2.0 compatible
- Automatic reconnect
- Configurable connection and session pool sizes
1.2. Supported standards and protocols
AMQ JMS Pool supports version 2.0 of the Java Message Service API.
1.3. Supported configurations
Refer to Red Hat AMQ 7 Supported Configurations on the Red Hat Customer Portal for current information regarding AMQ JMS Pool supported configurations.
1.4. Document conventions
The sudo command
In this document,
sudo is used for any command that requires root privileges. Exercise caution when using
sudo because any changes can affect the entire system. For more information about
sudo, see Using the sudo command.
In this document, all file paths are valid for Linux, UNIX, and similar operating systems (for example,
/home/andrea). On Microsoft Windows, you must use the equivalent Windows paths (for example,
This document contains code blocks with variables that you must replace with values specific to your environment. Variable text is enclosed in arrow braces and styled as italic monospace. For example, in the following command, replace
<project-dir> with the value for your environment:
$ cd <project-dir>