History

Clebert Suconic b8c64590f9 [maven-release-plugin] prepare for next development iteration		2021-08-09 11:58:28 -04:00
..
src/main/java/org/apache/activemq/artemis/jms/example	ARTEMIS-765 Improve Checkstyle	2016-09-30 11:12:09 -04:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2021-08-09 11:58:28 -04:00
readme.md	ARTEMIS-1562 Refactor example documentation	2017-12-15 14:54:16 +00:00

readme.md

JMS Application-Layer Failover Example

To run the example, simply type mvn verify from this directory. This example will always spawn and stop multiple brokers.

ActiveMQ Artemis implements fully transparent automatic failover of connections from a live node to a backup node which requires no special coding. This is described in a different example and requires broker replication.

However, ActiveMQ Artemis also supports Application-Layer failover which is useful in the case where replication is not enabled.

With Application-Layer failover, it's up to the application to register a JMS ExceptionListener with ActiveMQ Artemis. This listener will then be called by ActiveMQ Artemis in the event that connection failure is detected.

User code in the ExceptionListener can then recreate any JMS Connection, Session, etc on another node and the application can continue.

Application-Layer failover is an alternative approach to High Availability (HA).

Application-Layer failover differs from automatic failover in that some client side coding is required in order to implement this. Also, with Application-Layer failover, since the old Session object dies and a new is created, any uncommitted work in the old Session will be lost, and any unacknowledged messages might be redelivered.

For more information on ActiveMQ Artemis failover and HA, and clustering in general, please see the clustering section of the user manual.