Skip to content

vinicius-martinez/amq7-overview

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

15 Commits
.gitignore
.gitignore
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 

Repository files navigation

Introduction

This is a simple demo showcasing some of AMQ7 features/concepts such as: Broker, Client, Cluster, Security and Interconnect;

For additional details, please refer to Additional References section;

Environment

Demo Script:

  1. Installing AMQ-7.2 Broker
  2. Create a Broker
  3. Explore AMQ-7.2 Console
  4. Configure AMQ-7.2 Broker Settings
  5. Explore AMQ Producer/Consumer Tools
  6. Create Java/JMS and NodeJS Clients
  7. Master/Slave FailOver - Shared Storage
  8. Client FailOver

Installing AMQ-7.2 Broker 

unzip amq-broker-7.2.0-bin.zip

  • Check if the amq-broker-7.2.0 directory is successfully created and the following directories are within it:

    • from now on we're going to refer to $AMQ_HOME as the current location of you amq-7.2 broker installation
$ ls -l
total 72
-rw-r--r--@  1 vmartine  staff  22122 Jun 21 04:10 LICENSE
-rw-r--r--@  1 vmartine  staff    179 Jun 21 04:10 NOTICE
-rw-r--r--@  1 vmartine  staff   5391 Jun 21 04:10 README.html
drwxrwxr-x@  5 vmartine  staff    160 Jun 21 04:40 bin
drwxr-xr-x@  3 vmartine  staff     96 Nov  7 17:10 docs
drwxr-xr-x@  3 vmartine  staff     96 Nov  7 17:10 etc
drwxr-xr-x@  7 vmartine  staff    224 Nov  7 17:10 examples
drwxr-xr-x@ 55 vmartine  staff   1760 Nov  7 17:10 lib
drwxrwxr-x@  7 vmartine  staff    224 Jun 21 04:40 schema
drwxr-xr-x@ 16 vmartine  staff    512 Nov  7 17:10 web

Create a Broker

  • Create a brokers directory within $AMQ_HOME:
    • this is step is optional, however it's a good practice since we can easily perform administrative tasks such as cleanup, backup and restore without compromising the default AMQ7 files
cd *$AMQ_HOME*
mkdir brokers
  • Create a broker (e.g broker01):
./bin/artemis create brokers/broker01

  • Inform both username and passwords of your choice (e.g admin / admin) and set anonymous access to Y;

  • Check if broker01 directory has been created within $AMQ_HOME and the following directories are present:

$ ll -l
total 0
drwxr-xr-x   9 vmartine  staff  288 Nov  7 18:12 .
drwxr-xr-x   3 vmartine  staff   96 Nov  7 17:51 ..
drwxr-xr-x   4 vmartine  staff  128 Nov  7 17:51 bin
drwxr-xr-x   6 vmartine  staff  192 Nov  7 18:12 data
drwxr-xr-x  11 vmartine  staff  352 Nov  7 17:51 etc
drwxr-xr-x   2 vmartine  staff   64 Nov  7 17:51 lib
drwxr-xr-x   3 vmartine  staff   96 Nov  7 18:12 log
drwxr-xr-x   2 vmartine  staff   64 Nov  7 18:12 tmp
  • Navigate to broker01 directory and start this instance:
cd $AMQ_HOME/brokers/broker01/
./bin/artemis run

Explore AMQ-7.2 Console

  • By default AMQ 7.2 Console is available at port 8161, therefore in order to access it just open a browser of your choice and try to access http://localhost:8161 using the credentials informed on Lab 2

Configure AMQ-7.2 Broker

  • Navigate to broker01 directory and review all files within this directory. Specially broker.xml and artemis.profile;

  • Remove all acceptors configuration within broker.xml except artemis which runs on port 61616:

<acceptors>
  <acceptor name="artemis">tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300</acceptor>
</acceptors>
  • Restart broker01 instance:
cd $AMQ_HOME/brokers/broker01/
./bin/artemis run
  • Please notice that only acceptor running on 61616 is available:
2018-11-07 21:38:49,511 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started NIO Acceptor at 0.0.0.0:61616 for protocols [CORE,MQTT,AMQP,STOMP,HORNETQ,OPENWIRE]
  • While broker01 is up and running edit broker.xml once again adding a new address within addresses settings. Example:
<addresses>
  ...
  <address name="address.broker01">
    <anycast>
      <queue name="myFirstQueue"/>
      <queue name="mySecondQueue"/>
    </anycast>
  </address>
  • Finally wait up to 5 seconds and check your broker log for the upcoming info message about a new deployment:
2018-11-07 22:06:59,292 INFO  [org.apache.activemq.artemis.core.server] AMQ221003: Deploying queue myFirstQueue on address address.broker01
2018-11-07 22:06:59,302 INFO  [org.apache.activemq.artemis.core.server] AMQ221003: Deploying queue mySecondQueue on address address.broker01

Explore AMQ Producer/Consumer Tools

  • While broker01 is up and running, open a new terminal and execute:
./bin/artemis producer --destination address.broker01 --message-count 30 --url tcp://localhost:61616
  • The following output is expected:
./bin/artemis producer --destination address.broker01 --message-count 30 --url tcp://localhost:61616
Producer ActiveMQQueue[address.broker01], thread=0 Started to calculate elapsed time ...

Producer ActiveMQQueue[address.broker01], thread=0 Produced: 30 messages
Producer ActiveMQQueue[address.broker01], thread=0 Elapsed time in second : 0 s
Producer ActiveMQQueue[address.broker01], thread=0 Elapsed time in milli second : 97 milli seconds

  • Access AMQ Console http://localhost:8161 and browse: 0.0.0.0 -> addresses -> address.broker01 -> queues -> anycast

  • Since we did not specify a queue or topic all messages are dispatched and balanced between all locations within our address definition, therefore you should see 10 messages on each destination in Message Count property;

  • Open a new terminal for each consumer and execute:

cd $AMQ_HOME/brokers/broker01/
./bin/artemis consumer --destination address.broker01 --url tcp://localhost:61616
./bin/artemis consumer --destination myFirstQueue --url tcp://localhost:61616
./bin/artemis consumer --destination mySecondQueue --url tcp://localhost:61616
  • Plase notice that Message Count property for each destination is now 0;

Create Java/JMS and NodeJS Clients

  • Download both AMQ JMS Client and JavaScript Client from Red Hat Developers AMQ Download

  • Uncompress both files in a directory of your choice

  • Make sure you have configured your settings.xml enabling Red Hat repositories. Example:

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <profiles>

        <!-- Configure the AMQ7 Maven repository -->
        <profile>
            <id>amq-qpid-jms</id>
            <repositories>
                <repository>
                    <id>amq-qpid-jms</id>
                    <url>file:///path/to/extracted/maven-repository</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>amq7-repository</id>
                    <url>file:///path/to/extracted/maven-repository</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </pluginRepository>
            </pluginRepositories>
        </profile>
        <!-- Configure the JBoss GA Maven repository -->
        <profile>
            <id>jboss-ga-repository</id>
            <repositories>
                <repository>
                    <id>jboss-ga-repository</id>
                    <url>https://maven.repository.redhat.com/ga</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>jboss-ga-repository</id>
                    <url>https://maven.repository.redhat.com/ga</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </pluginRepository>
            </pluginRepositories>
        </profile>
        <!-- Configure the JBoss Early Access Maven repository -->
        <profile>
            <id>jboss-earlyaccess-repository</id>
            <repositories>
                <repository>
                    <id>jboss-earlyaccess-repository</id>
                    <url>https://maven.repository.redhat.com/earlyaccess/all/</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </repository>
            </repositories>
            <pluginRepositories>
                <pluginRepository>
                    <id>jboss-earlyaccess-repository</id>
                    <url>https://maven.repository.redhat.com/earlyaccess/all/</url>
                    <releases>
                        <enabled>true</enabled>
                    </releases>
                    <snapshots>
                        <enabled>false</enabled>
                    </snapshots>
                </pluginRepository>
            </pluginRepositories>
        </profile>
    </profiles>
    <activeProfiles>
        <activeProfile>amq-qpid-jms</activeProfile>
        <activeProfile>jboss-ga-repository</activeProfile>
        <activeProfile>jboss-earlyaccess-repository</activeProfile>
    </activeProfiles>

</settings>
  • From AMQ JMS Client directory, go to examples folder an run a clean/install:
cd apache-qpid-jms-0.34.0.redhat-00002/examples
mvn clean install

  • Review jndi.properties and HelloWorld.java files for a better comprehension;

  • Execute the following command in order to send and consume a Hello World Message

cd apache-qpid-jms-0.34.0.redhat-00002/examples
mvn clean install
mvn clean package dependency:copy-dependencies -DincludeScope=runtime -DskipTests
java -cp "target/classes/:target/dependency/*" org.apache.qpid.jms.example.HelloWorld

Hello world!

  • Access AMQ Console and notice that we have a new queue under addresses;

  • From JavaScript Client (nodejs-rhea-0.2.15-1) directory, execute:

npm install debug
npm install yargs
  • From nodejs-rhea-0.2.15-1/node_modules/rhea directory execute:
npm install
npm run browserify
  • Switch back to nodejs-rhea-0.2.15-1 folder and create a new directory (e.g example):
mkdir example
  • Create a send.js file with the following content:
"use strict";

var rhea = require("rhea");
var url = require("url");

if (process.argv.length !== 5) {
    console.error("Usage: send.js <connection-url> <address> <message-body>");
    process.exit(1);
}

var conn_url = url.parse(process.argv[2]);
var address = process.argv[3];
var message_body = process.argv[4];

var container = rhea.create_container();

container.on("sender_open", function (event) {
    console.log("SEND: Opened sender for target address '" +
                event.sender.target.address + "'");
});

container.on("sendable", function (event) {
    var message = {
        "body": message_body
    };

    event.sender.send(message);

    console.log("SEND: Sent message '" + message.body + "'");

    event.sender.close();
    event.connection.close();
});

var opts = {
    host: conn_url.hostname,
    port: conn_url.port || 61616
};

var conn = container.connect(opts);
conn.open_sender(address);
  • Create a receive.js file with the following content:
"use strict";

var rhea = require("rhea");
var url = require("url");

if (process.argv.length !== 4 && process.argv.length !== 5) {
    console.error("Usage: receive.js <connection-url> <address> [<message-count>]");
    process.exit(1);
}

var conn_url = url.parse(process.argv[2]);
var address = process.argv[3];
var desired = 0;
var received = 0;

if (process.argv.length === 5) {
    desired = parseInt(process.argv[4]);
}

var container = rhea.create_container();

container.on("receiver_open", function (event) {
    console.log("RECEIVE: Opened receiver for source address '" +
                event.receiver.source.address + "'");
});

container.on("message", function (event) {
    var message = event.message;

    console.log("RECEIVE: Received message '" + message.body + "'");

    received++;

    if (received == desired) {
        event.receiver.close();
        event.connection.close();
    }
});

var opts = {
    host: conn_url.hostname,
    port: conn_url.port || 61616
};

var conn = container.connect(opts);
conn.open_receiver(address);
  • Open a new terminal and start receive.js. Example:
node receive.js amqp://localhost node-queue
RECEIVE: Opened receiver for source address 'node-queue'
  • Open a new terminal and send some messages via send.js. Example:
node send.js amqp://localhost node-queue hello
SEND: Opened sender for target address 'node-queue'
SEND: Sent message 'hello'

node send.js amqp://localhost node-queue hello2
SEND: Opened sender for target address 'node-queue'
SEND: Sent message 'hello2'
  • Switch back to the receive terminal and check for the incoming consumed messages:
RECEIVE: Received message 'hello'
RECEIVE: Received message 'hello2'

Master/Slave FailOver - Shared Storage

  • Create two (2) new brokers (e.g master/slave). Example:
./bin/artemis create brokers/master --name master --user admin --password admin --allow-anonymous
./bin/artemis create brokers/slave --name slave --user admin --password admin --allow-anonymous --port-offset 1
  • Edit brokers/master/etc/broker.xml updating the following attributes: paging-directory, bindings-directory, journal-directory, and large-messages-directory. Example:
<paging-directory>../shared/data/paging</paging-directory>
<bindings-directory>../shared/data/bindings</bindings-directory>
<journal-directory>../shared/data/journal</journal-directory>
<large-messages-directory>../shared/data/large-messages</large-messages-directory>
  • Include ha-configuration under master tag. Example:
<connectors>
  <connector name="master-connector">tcp://localhost:61616</connector>
  <connector name="slave-connector">tcp://localhost:61617</connector>
</connectors>

<cluster-user>admin</cluster-user>
<cluster-password>admin</cluster-password>

<cluster-connections>
  <cluster-connection name="static-cluster">
    <connector-ref>master-connector</connector-ref>
    <static-connectors>
      <connector-ref>slave-connector</connector-ref>
    </static-connectors>
  </cluster-connection>
</cluster-connections>

<ha-policy>
  <shared-store>
    <master>
      <failover-on-shutdown>true</failover-on-shutdown>
    </master>
  </shared-store>
</ha-policy>
  • Start master broker:
./brokers/master/bin/artemis run
  • Edit brokers/slave/etc/broker.xml updating the following attributes: paging-directory, bindings-directory, journal-directory, and large-messages-directory. Example:
<paging-directory>../shared/data/paging</paging-directory>
<bindings-directory>../shared/data/bindings</bindings-directory>
<journal-directory>../shared/data/journal</journal-directory>
<large-messages-directory>../shared/data/large-messages</large-messages-directory>
  • Include ha-configuration under slave tag. Example:
<connectors>
  <connector name="master-connector">tcp://localhost:61616</connector>
  <connector name="slave-connector">tcp://localhost:61617</connector>
</connectors>

<cluster-user>admin</cluster-user>
<cluster-password>admin</cluster-password>

<cluster-connections>
  <cluster-connection name="static-cluster">
    <connector-ref>slave-connector</connector-ref>
    <static-connectors>
      <connector-ref>master-connector</connector-ref>
    </static-connectors>
  </cluster-connection>
</cluster-connections>

<ha-policy>
  <shared-store>
    <slave>
      <failover-on-shutdown>true</failover-on-shutdown>
      <allow-failback>true</allow-failback>
    </slave>
  </shared-store>
</ha-policy>
  • Start slave broker:
./brokers/slave/bin/artemis run
  • Open a new terminal and send some messages to master. Example:
$AMQ_HOME/bin/artemis producer --verbose --user admin --password admin --message-count 100 --url 'tcp://localhost:61616'
  • Shutdown master broker (CTRL+C). A similar output should be diplayed in slave terminal informing that this broker is now active:
2018-11-08 01:00:33,002 WARN  [org.apache.activemq.artemis.core.client] AMQ212037: Connection failure has been detected: AMQ119015: The connection was disconnected because of server shutdown [code=DISCONNECTED]
2018-11-08 01:00:33,002 WARN  [org.apache.activemq.artemis.core.client] AMQ212037: Connection failure has been detected: AMQ119015: The connection was disconnected because of server shutdown [code=DISCONNECTED]
2018-11-08 01:00:33,231 WARN  [org.apache.activemq.artemis.core.client] AMQ212004: Failed to connect to server.
2018-11-08 01:00:33,474 INFO  [org.apache.activemq.artemis.core.server] AMQ221003: Deploying queue DLQ on address DLQ
2018-11-08 01:00:33,474 INFO  [org.apache.activemq.artemis.core.server] AMQ221003: Deploying queue ExpiryQueue on address ExpiryQueue
2018-11-08 01:00:33,690 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started NIO Acceptor at 0.0.0.0:61617 for protocols [CORE,MQTT,AMQP,STOMP,HORNETQ,OPENWIRE]
2018-11-08 01:00:33,692 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started NIO Acceptor at 0.0.0.0:5446 for protocols [HORNETQ,STOMP]
2018-11-08 01:00:33,694 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started NIO Acceptor at 0.0.0.0:5673 for protocols [AMQP]
2018-11-08 01:00:33,695 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started NIO Acceptor at 0.0.0.0:1884 for protocols [MQTT]
2018-11-08 01:00:33,698 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started NIO Acceptor at 0.0.0.0:61614 for protocols [STOMP]
2018-11-08 01:00:33,698 INFO  [org.apache.activemq.artemis.core.server] AMQ221010: Backup Server is now live
  • Start the consumer and check for the incoming messages:
$AMQ_HOME/bin/artemis consumer --verbose --user admin --password admin --message-count 100 --url 'tcp://localhost:61617'

Consumer ActiveMQQueue[TEST], thread=0 Received test message: 0
Received text sized at 15
Consumer ActiveMQQueue[TEST], thread=0 Received test message: 1
Received text sized at 15
Consumer ActiveMQQueue[TEST], thread=0 Received test message: 2
Received text sized at 15
...
Consumer ActiveMQQueue[TEST], thread=0 Consumed: 100 messages
Consumer ActiveMQQueue[TEST], thread=0 Consumer thread finished
  • Restart master broker and check form a similar output should in slave terminal:
2018-11-08 01:06:49,769 INFO  [org.apache.activemq.artemis.core.server] AMQ221109: Apache ActiveMQ Artemis Backup Server version 2.6.1.amq-720004-redhat-1 [f522976c-e300-11e8-8521-acde48001122] started, waiting live to fail before it gets active
2018-11-08 01:06:49,774 INFO  [org.apache.activemq.artemis.core.server] AMQ221031: backup announced

Client FailOver

  • Start both master and slave brokers:
./brokers/masters/bin/artemis run
./brokers/slave/bin/artemis run
  • Open a new terminal and send some messages to master. Example:
$AMQ_HOME/bin/artemis producer --verbose --user admin --password admin --message-count 100 --url 'tcp://localhost:61616' --destination failover
  • Shutdown master broker (CTRL+C) and ensure that slave broker is now active:
2018-11-08 01:15:11,173 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started NIO Acceptor at 0.0.0.0:61617 for protocols [CORE,MQTT,AMQP,STOMP,HORNETQ,OPENWIRE]
2018-11-08 01:15:11,176 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started NIO Acceptor at 0.0.0.0:5446 for protocols [HORNETQ,STOMP]
2018-11-08 01:15:11,178 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started NIO Acceptor at 0.0.0.0:5673 for protocols [AMQP]
2018-11-08 01:15:11,180 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started NIO Acceptor at 0.0.0.0:1884 for protocols [MQTT]
2018-11-08 01:15:11,182 INFO  [org.apache.activemq.artemis.core.server] AMQ221020: Started NIO Acceptor at 0.0.0.0:61614 for protocols [STOMP]
2018-11-08 01:15:11,182 INFO  [org.apache.activemq.artemis.core.server] AMQ221010: Backup Server is now live

  • Download legacy activemq client from MVN Repository

  • Start the consumer using Client Failover features:

java -jar activemq-all-5.14.5.jar consumer --brokerUrl 'failover:(tcp://localhost:61616,tcp://localhost:61617)' --user admin --password admin --destination queue://failover
  • The following output is expected:
java -jar activemq-all-5.14.5.jar consumer --brokerUrl 'failover:(tcp://localhost:61616,tcp://localhost:61617)' --user admin --password admin --destination queue://failover
 INFO | Connecting to URL: failover:(tcp://localhost:61616,tcp://localhost:61617) (admin:admin)
 INFO | Consuming queue://failover
 INFO | Sleeping between receives 0 ms
 INFO | Running 1 parallel threads
 INFO | Successfully connected to tcp://localhost:61617
 INFO | consumer-1 wait until 1000 messages are consumed
 INFO | consumer-1 Received test message: 0
 INFO | consumer-1 Received test message: 1
 INFO | consumer-1 Received test message: 2
 ...

Additional References

About

No description, website, or topics provided.

Resources

Readme

License

Apache-2.0 license
Activity

Stars

1 star

Watchers

2 watching

Forks

2 forks
Report repository

Releases

No releases published

Packages

No packages published