order

Infrastructure

• zookeeper
  Program Coordination Service Framework for automatic scheduling of multiple activemqs. After an activemq service goes down, zookeeper automatically schedules one of the normal activemq services in the cluster to become the master host to continue serving.
• activemq
  Message queuing framework, we will deploy multiple activemq services

Plan

Suppose we have three servers:

• 192.168.0.200
  Deploy activemq-master, zookeeper
• 192.168.0.201
  Deployment of activemq-slave01
• 192.168.0.202
  Deployment of activemq-slave02

Cluster building

Configure zookeeper

• Decompress zookeeper-3.4.9.tar.gz

$ tar -zxvf zookeeper-3.4.9.tar.gz

• Create zookeeper configuration file by example

$ cp -R zoo_sample.cfg /home/zookeeper-3.4.9/conf/zoo.cfg

• Configure zookeeper-3.4.9/conf/zoo.cfg as follows:

# The number of milliseconds of each tick
tickTime=2000
# The number of ticks that the initial 
# synchronization phase can take
initLimit=10
# The number of ticks that can pass between 
# sending a request and getting an acknowledgement
syncLimit=5
# the directory where the snapshot is stored.
# do not use /tmp for storage, /tmp here is just 
# example sakes.
dataDir=/tmp/zookeeper
# the port at which the clients will connect
clientPort=2181
# the maximum number of client connections.
# increase this if you need to handle more clients
#maxClientCnxns=60
#
# Be sure to read the maintenance section of the 
# administrator guide before turning on autopurge.
#
# http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_maintenance
#
# The number of snapshots to retain in dataDir
#autopurge.snapRetainCount=3
# Purge task interval in hours
# Set to "0" to disable auto purge feature
#autopurge.purgeInterval=1

Configure activemq

Actemq configuration, which will configure three services according to the plan, will be handed over to zookeeper for scheduling.

• install
  Here, instead of elaborating on the installation of activemq, see "ActiveMQ Tutorial (1) - Installation": http://blog.csdn.net/eugeneheen/article/details/55190552

• Configure the core configuration file/home/apache-activemq-5.9.1-bin/activemq.xml

<beans
  xmlns="http://www.springframework.org/schema/beans"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
  http://activemq.apache.org/schema/core http://activemq.apache.org/schema/core/activemq-core.xsd">

    <!-- Allows us to use system properties as variables in this configuration file -->
    <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
        <property name="locations">
            <value>file:${activemq.conf}/credentials.properties</value>
        </property>
    </bean>

   <!-- Allows accessing the server log -->
    <bean id="logQuery" class="io.fabric8.insight.log.log4j.Log4jLogQuery"
          lazy-init="false" scope="singleton"
          init-method="start" destroy-method="stop">
    </bean>

    <!--
        The <broker> element is used to configure the ActiveMQ broker.
    -->
    <broker xmlns="http://activemq.apache.org/schema/core" brokerName="broker-test" dataDirectory="${activemq.data}">

        <destinationPolicy>
            <policyMap>
              <policyEntries>
                <policyEntry topic=">" >
                    <!-- The constantPendingMessageLimitStrategy is used to prevent
                         slow topic consumers to block producers and affect other consumers
                         by limiting the number of messages that are retained
                         For more information, see:

                         http://activemq.apache.org/slow-consumer-handling.html

                    -->
                  <pendingMessageLimitStrategy>
                    <constantPendingMessageLimitStrategy limit="1000"/>
                  </pendingMessageLimitStrategy>
                </policyEntry>
              </policyEntries>
            </policyMap>
        </destinationPolicy>


        <!--
            The managementContext is used to configure how ActiveMQ is exposed in
            JMX. By default, ActiveMQ uses the MBean server that is started by
            the JVM. For more information, see:

            http://activemq.apache.org/jmx.html
        -->
        <managementContext>
            <managementContext createConnector="false"/>
        </managementContext>

        <!--
            Configure message persistence for the broker. The default persistence
            mechanism is the KahaDB store (identified by the kahaDB tag).
            For more information, see:

            http://activemq.apache.org/persistence.html
        -->
        <persistenceAdapter>
            <!--<kahaDB directory="${activemq.data}/kahadb"/>-->
        <replicatedLevelDB directory="${activemq.data}/kahadb" 
        replicas="3"
        bind="tcp://0.0.0.0:0"
        zkAddress="192.168.0.201:2181"
        zkSessionTimeout="10s"
        hostname="192.168.0.201"
        zkPath="/home/leveldb-stores"
        />
        </persistenceAdapter>


          <!--
            The systemUsage controls the maximum amount of space the broker will
            use before disabling caching and/or slowing down producers. For more information, see:
            http://activemq.apache.org/producer-flow-control.html
          -->
          <systemUsage>
            <systemUsage>
                <memoryUsage>
                    <memoryUsage percentOfJvmHeap="70" />
                </memoryUsage>
                <storeUsage>
                    <storeUsage limit="100 gb"/>
                </storeUsage>
                <tempUsage>
                    <tempUsage limit="50 gb"/>
                </tempUsage>
            </systemUsage>
        </systemUsage>

        <!--
            The transport connectors expose ActiveMQ over a given protocol to
            clients and other brokers. For more information, see:

            http://activemq.apache.org/configuring-transports.html
        -->
        <transportConnectors>
            <!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB -->
            <transportConnector name="openwire" uri="tcp://0.0.0.0:51511?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
            <transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
            <transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
            <transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
            <transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
        </transportConnectors>

        <!-- destroy the spring context on shutdown to stop jetty -->
        <shutdownHooks>
            <bean xmlns="http://www.springframework.org/schema/beans" class="org.apache.activemq.hooks.SpringContextHook" />
        </shutdownHooks>

    </broker>

    <!--
        Enable web consoles, REST and Ajax APIs and demos
        The web consoles requires by default login, you can disable this in the jetty.xml file

        Take a look at ${ACTIVEMQ_HOME}/conf/jetty.xml for more details
    -->
    <import resource="jetty.xml"/>

</beans>

Configuration details:
a. Unified setup of brokerName
All activemq services must be fully configured with brokerName as a unified value

<broker xmlns="http://activemq.apache.org/schema/core" brokerName="broker-test" dataDirectory="${activemq.data}">

b. Configuring persistence adapter
There are three main ways to set persistence adapter persistence mode: kahaDB (default mode), database persistence and levelDB (activemq v5.9.0 provides support)

 <persistenceAdapter>
     <!--<kahaDB directory="${activemq.data}/kahadb"/>-->
    <replicatedLevelDB directory="${activemq.data}/kahadb" 
    replicas="3"
    bind="tcp://0.0.0.0:0"
    zkAddress="192.168.0.201:2181"
    zkSessionTimeout="10s"
    hostname="192.168.0.201"
    zkPath="/home/leveldb-stores"
    />
</persistenceAdapter>

c. Configure the transportConnector message port

<transportConnectors>
    <transportConnector name="openwire" uri="tcp://0.0.0.0:51511?maximumConnections=1000&amp;wireFormat.maxFrameSize=104857600"/>
</transportConnectors>

• Configure the activemq management platform access port / home/apache-activemq-5.9.1-bin/jetty.xml

<bean id="jettyPort" class="org.apache.activemq.web.WebConsolePort" init-method="start">
        <property name="host" value="0.0.0.0"/>
        <property name="port" value="8161"/>
</bean>

Start up service

• Start zookeeper
  zookeeper service must be better than activemq service startup

$ {zookeeper_home}/bin/zkServer.sh start

• Start activemq
  Start activemq service in turn

$ {activemq_home}/bin/active start

Managing activemq

zookeeper's strategy is to select one of the three activemq servers to run, while the other two are waiting to run, just to synchronize the master and slave on the data.

So, after starting the ZooKeeper server and ActiveMQ server, access http://192.168.0.200.1:8161/admin/ , http://192.168.0.201:8161/admin/, http://192.168.0.202:8161/admin/ There will only be one success.

Client Connection Actemq

Using Spring to manage beans, the configuration is as follows:

 <bean id="activeMQConnectionFactory" class="org.apache.activemq.ActiveMQConnectionFactory">
        <property name="userName" value="admin" />
        <property name="password" value="admin" />
        <property name="brokerURL" value="failover:(tcp://192.168.0.201:51511,tcp://192.168.0.201:51512,tcp://192.168.0.201:51513)?initialReconnectDelay=100" />
</bean>