getting_started_with_activemq | Getting Started with ActiveMQ

This project includes a number of example configurations showing various ActiveMQ High Availability scenarios. These include: Master-Slave, Network of Brokers, and Network of Master-Slave Brokers. This project also includes a simple JMS Queue (point to point) message producer and message consumer. Note: All of this code will run correctly against either Apache ActiveMQ 5.9.0 or JBoss A-MQ 6.2.0 as both internally use the same ActiveMQ 5.9.0 code base. The instructions on how to start (command line) the brokers from an ActiveMQ install will not work with JBoss A-MQ (e.g. bin/amq) as JBoss A-MQ has ActiveMQ deployed within an Apache Karaf container to allow for runtime updates to configuration information (versus needing to restart the broker in the case on Apache ActiveMQ). There are additional steps required to use these provided broker configuration files and deploy them correctly to JBoss A-MQ with its Fabric based configuration system. JBoss A-MQ’s install contains an extras directory with a support version of the Apache ActiveMQ 5.9.0 binary install. The Master-Slave configuration enables quick activation of a broker instance to continue processing of messages stored within a message persistence store. It utilizes a shared file system, in this case the same local directory, with both brokers referencing this same directory. The first broker instance to acquire a file lock is considered the 'master', and all subsequent broker instances waiting for the file lock are considered 'slave'. To run this sample,.
all instructions assume you are executing from the top level directory of this project
it is assumed you have Apache Maven installed, and that you are familiar with its usage
assumes you are using Apache ActiveMQ 5.9.0 or later, or JBoss A-MQ 6.2.0 or later