High availability using JMS clustering

IBM Supports JMS clustering, which provides high availability for systems that require near-zero downtime.

A JMS cluster configuration comprises two or more JMS servers. If a node in the JMS cluster fails, any messages sent to the failed node are seamlessly transitioned to another node in the cluster. This automatic failover to another node when one node fails ensures that messages are not lost, and it provides you with high availability for your system.

High availability is supported for the following integration services, agents, and message queue application servers:

  • IBM MQ
  • WebSphere Default Messaging
  • Apache ActiveMQ
  • Oracle WebLogic JMS
Note: The persistence flags are set for senders and sessions for messages sent to a given JMS vendor's queue to guarantee persistence. When persistence flags are not specified by the configuration of the service, no persistence flags are set on senders and sessions. Therefore, you should be aware of the behavior of your vendor's queues when no session or sender persistence recommendations are given.