ActiveMQ Container
Java Messaging Service for Commerce integrations.
Prerequisites
The activemq container image must be built and available. For information on building container images, see Building Container Images.
Suitable Environment Types
ActiveMQ is a required component for Self-Managed Commerce. The containerized ActiveMQ implementation can be suitable for all types of Self-Managed Commerce environments, including production, provided that a suitable persistent volume is used.
| Include in Development and QA Environments? | Include in Authoring Environments? | Include in Live Environments? |
|---|---|---|
| Yes | Yes | Yes |
Other ActiveMQ implementations can be used in place of the provided containerized implementation. For information about supported message broker options, see Supported Technologies.
Configuration
The sections below describe typical configurations.
Note about production sizing and tuning
The values shared in this document are suggestions that are known to work well in typical scenarios.
Resource allocation
Resource allocation can vary by usage and load. Below are typical values.
| Resource | Non Production | Production Like (See Note) |
|---|---|---|
| Container Memory (MB) | 1280 | 1280 |
| Container Cores | 1 | 1 |
Scaling and replicas
ActiveMQ cannot be horizontally scaled.
| Configuration | Non Production | Production Like (See Note) |
|---|---|---|
| Minumim Replicas | 1 | 1 |
| Maximum Replicas | 1 | 1 |
Ports
| Port | Non Production | Production | Purpose | Comment |
|---|---|---|---|---|
| 61616 | Yes | Yes | Java Messaging Service (JMS). | This port should only be exposed internally, ideally only to the Commerce services. |
| 8161 | Yes | Yes | ActiveMQ administration tool. | This port should only be exposed internally, ideally only to deveopment or operations users with a suitable business need. |
Health, Liveness and Readiness
You can use a TCP socket connection on either of the TCP ports, to validate the availability of ActiveMQ.
Volumes
| Mount Point | Purpose | Comment |
|---|---|---|
| /ep/efs | Persist unprocessed JMS messages. | The most important characteristic of this volume is that it is available wherever the container might run. This is to ensure that, if one instance of the container dies and new instance replaces it in another zone or on another host, then any previously un-processed messages can be found and processed. A recommended size for this volume is 100GB. |
Environment Variables
The ActiveMQ container has limited configurability and does not support the environment variables used by other Commerce applications.