How to Setup Replicated LevelDB Persistence in Apache ActiveMQ 5.9--转载

原文地址：https://simplesassim.wordpress.com/2013/11/03/how-to-setup-replicated-leveldb-persistence-in-apache-activemq-5-9/

1) Install Apache ZooKeeper.

2) Change the persistence adapter in the <Apache ActiveMQ Install Dir>/etc/activemq.xml file:

1 2 3

<persistenceAdapter>   <replicatedLevelDB directory="activemq-data" replicas="..." bind="tcp://0.0.0.0:61619" zkAddress="host:2181" zkPath="/activemq/leveldb-stores" /> </persistenceAdapter>

3) Start Apache ZooKeeper.

4) Start Apache ActiveMQ.

You can find more details here.

another article about how to set up：

Setup ActiveMQ, Zookeeper, and Replicated LevelDB running in JDK 8 and CentOS

原文地址：http://www.elasticcloudapps.com/page0/files/c1f6bea32e025aa68542a95f9d664ea9-12.html

This guide describes the step-by-step guide to setup ActiveMQ to use replicated LevelDB persistence with Zookeeper. CentOS environment is used for servers. Zookeeper is used to replicate the LevelDB to support Master/Slave activeMQs. Three VMware instances are used with 2 Core processes, 2G RAM and 20G disk space. For simplicity, stop the IPtable service (firewall) in CentOS. If IPTable is required then you need to open set of ports. List of port numbers are included in pre-setup work section.

Overview
ActiveMQ cluster environment includes following
1 Three VM instances with CentOS os AND JDK 8
2 Three ActiveMQ instances.
3 Three Zookeeper instances.

Pre-install

Following ports are required to open in Iptables host firewall.

• Zookeeper

• • 2181 – the port that clients will use to connect to the ZK ensemble
• • 2888 – port used by ZK for quorum election
• • 3888 – port used by ZK for leader election

• ActiveMQ

• • 61616 – default Openwire port
• • 8161 – Jetty port for web console
• • 61619 – LevelDB peer-to-peer replication port for ActiveMQ slaves.

• To check Iptables status.

• • service iptables status

• To stop iptables service

• • service iptables save
• • service iptables stop
• • chkconfig iptables off

• To start again

• • service iptables start
• • chkconfig iptables on

• Setup proper hostname, edit  following files

• • Update HOSTNAME value in /etc/sysconfig/network : E.g: HOSTNAME=msgq1.dev.int
• • Add host name with IP address of the machine in /etc/hosts: E.g: 192.168.163.160   msgq1.dev.int  msgqa1
• • Restart the instance and repeat same process each instances.

Installation

Java JDK

• Download JDK 8 from http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
• Extract JdK-8*.tar.gz to a folder of your choice (I used ~/Dev/server). This will create folder ~/Dev/server/jdk1.8.0_20.
• Set up JAVA_HOME directory.
• To setup for all users edit /etc/profile and add following line export JAVA_HOME=HOME_DIR/Dev/server/jdk1.8.0_20.

Zookeeper

• Download zookeeper from site http://zookeeper.apache.org/
• Extract the file into your folder of your choice. I have used ~/Dev/server/
• Create soft link zookeeper for extracted directory.
• For reliable ZooKeeper service, the ZK should be deployed in a cluster mode knows as ensemble.  As long as a majority of the ensemble are up, the service will be available.
• Goto conf directory and create zookeeper configuration directory.
• cd <zookeeper_install_dir>/conf
• Copy zoo_sample.cfg to  zoo.cfg
• Make sure the file has following lines

• • tickTime=2000initLimit=5 
    syncLimit=2 
    dataDir=~/Dev/server/data/zk 
    clientPort=2181

• Add following lines into zoo.cfg at the end.

• • server.1=zk1_IPADDRESS:2888:3888
    server.2=zk2_IPADDRESS:2888:3888
    server.3=zk3_IPADDRESS:2888:3888
• • zk1, zk2 & zk3 are IP addresses for the ZK servers.
• • Port 2181 is used to communicate with client
• • Port 2888 is used by peer ZK servers to communicate among themselves (Quorum port)
• • Port 3888 is used for leader election (Leader election port).

• The last three lines of the server.id=host:port:port format specifies that there are three nodes in the ensemble. In an ensemble, each ZooKeeper node must have a unique ID between 1 and 255. This ID is defined by creating a file named myid in the dataDir directory of each node. For example, the node with the ID 1 (server.1=zk1:2888:3888) will have a myid file at /home/sthuraisamy/Dev/server/data/zk with the text 1 inside it.
• Create myid file in data directory for zk1 ( server.1) and for other ZK servers as 2 & 3.

• • echo 1 > myid

ActiveMQ
Download activemq distribution from http://apache.mirror.nexicom.net/activemq/5.10.0/apache-activemq-5.10.0-bin.tar.gz

• Extract the file into your folder of your choice. I have used ~/Dev/server/
• Create soft link activemq for extracted directory.
• Do following

• • cd <active_mq_dir>/bin
• • chmod 755 activemq
• • <active_mq_dir>/bin/activemq start

• To confirm the activemq is listening on port 61616 or check the log file and confirm port listening messages are populated.

• • netstat -an|grep 61616

• In activemq config file, following bean classes define the settings

• • PropertyPlaceholderConfigurer
• • Credentials
• • Broker section

• • • constantPendingMessageLimitStrategy: limit the number of messages to be keep in memory for slow consumers.

• • Other settings to handle slower consumers, refer http://activemq.apache.org/slow-consumer-handling.html
• • Persistence adapter to define the storage to keep the messages.
• • For better performance

• • • Use NIO : Refer http://activemq.apache.org/configuring-transports.html#ConfiguringTransports-TheNIOTransport

• • Replicated LevelDB store using Zookeeper http://activemq.apache.org/replicated-leveldb-store.html
• • The settings need to be done in ActiveMQ after zookeeper is setup. Add following lines into conf/activemq.xml

• • • hostname should be assigned with separate IP address for each instance.

My approach was to get the software setup on a single VM instance in VM Ware fusion, and create two more clones to have three servers.  I have named the instances as messageq1, messageq2, and messageq3.  After starting instances confirm the myid file and IP address in the zoo.cfg are setup properly with new instance’s ip address.

After configured everything

• Start the Zookeeper instances in all three nodes : <zookeeper_dir>/bin/zk_Server.sh start
• Start the activeMQ instances in all three nodes : <activemq_dir>/bin/activemq start
• In my setup when I start the first node I didn’t find any issue. After I have started the second node, I found exception in the log file.

No IOExceptionHandler registered, ignoring IO exception | org.apache.activemq.broker.BrokerService | LevelDB IOExcepti
on handler.
java.io.IOException: com.google.common.base.Objects.firstNonNull(Ljava/lang/Object;Ljava/lang/ObjectLjava/lang/Object;
     at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:39)[activemq-client-5.10.0.jar:5.10.0]
     at org.apache.activemq.leveldb.LevelDBClient.might_fail(LevelDBClient.scala:552)[activemq-leveldb-store-5.10.0.jar:5.10.0]
     at org.apache.activemq.leveldb.LevelDBClient.replay_init(LevelDBClient.scala:657)[activemq-leveldb-store-5.10.0.jar:5.10.0]
     at org.apache.activemq.leveldb.LevelDBClient.start(LevelDBClient.scala:558)[activemq-leveldb-store-5.10.0.jar:5.10.0]
     at org.apache.activemq.leveldb.DBManager.start(DBManager.scala:648)[activemq-leveldb-store-5.10.0.jar:5.10.0]
     at org.apache.activemq.leveldb.LevelDBStore.doStart(LevelDBStore.scala:235)[activemq-leveldb-store-5.10.0.jar:5.10.0]
     at org.apache.activemq.leveldb.replicated.MasterLevelDBStore.doStart(MasterLevelDBStore.scala:110)[activemq-leveldb-store-5.10.0.jar:5.10.0]
     at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)[activemq-client-5.10.0.jar:5.10.0]
     at org.apache.activemq.leveldb.replicated.ElectingLevelDBStore$$anonfun$start_master$1.apply$mcV$sp(ElectingLevelDBStore.scala:226)[activemq-lev
eldb-store-5.10.0.jar:5.10.0]
     at org.fusesource.hawtdispatch.package$$anon$4.run(hawtdispatch.scala:330)[hawtdispatch-scala-2.11-1.21.jar:1.21]
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_20]
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_20]

After going through tickets in activeMQ  found following ticket has been reported https://issues.apache.org/jira/browse/AMQ-5225. Workaround described in the ticket will solve the issue. The work around for this issue,

1. remove pax-url-aether-1.5.2.jar from lib directory
2. comment out the log query section

To confirm ActiveMQ listening for request
◦ In master, check with netstat -an | grep 61616 and confirm the port is in listen mode.
◦ In slaves, you can run netstat -an | grep 6161 and output should show you slave binding port 61619

Post-Install
◦ For Zookeeper, set the Java heap size. This is very important to avoid swapping, which will seriously degrade ZooKeeper performance. To determine the correct value, use load tests, and make sure you are well below the usage limit that would cause you to swap. Be conservative - use a maximum heap size of 3GB for a 4GB machine.
◦ Increase the open file number to support 51200. E.g: limit -n 51200.
◦ Review linux network setting parameters : http://www.nateware.com/linux-network-tuning-for-2013.html#.VA8pN2TCMxo 
◦ Review ActiveMQ transports configuration settings : http://activemq.apache.org/configuring-transports.html
◦ Review ActiveMQ persistence configuration settings : http://activemq.apache.org/persistence.html
◦ Review zookeeper configuration settings : http://zookeeper.apache.org/doc/trunk/zookeeperAdmin.html#sc_configuration

Reference
◦ tickTime: the length of a single tick, which is the basic time unit used by ZooKeeper, as measured in milliseconds. It is used to regulate heartbeats, and timeouts. For example, the minimum session timeout will be two ticks.
◦ initLimit: Amount of time, in ticks , to allow followers to connect and sync to a leader. Increased this value as needed, if the amount of data managed by ZooKeeper is large.
◦ syncLimit: Amount of time, in ticks , to allow followers to sync with ZooKeeper. If followers fall too far behind a leader, they will be dropped.
◦ clientPort: The port to listen for client connections; that is, the port that clients attempt to connect to.
◦ dataDir: The location where ZooKeeper will store the in-memory database snapshots and, unless specified otherwise, the transaction log of updates to the database.

ActiveMQ configuration file from msgq1
    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">
    
        
            file:${activemq.conf}/credentials.properties
        
    
            scope="singleton" init-method="start" destroy-method="stop"> 
            dataDirectory="${activemq.data}">

<replicatedleveldb
                zkAddress="192.168.163.160:2181,192.168.163.161:2181,192.168.163.162:2181"
                directory=“~/Dev/server/activemq/data/leveldb"
                hostname="192.168.163.160"/>
  
                            class="org.apache.activemq.hooks.SpringContextHook"/>

ZK Configuration file
tickTime=2000
initLimit=5
syncLimit=2
dataDir=/home/sthuraisamy/Dev/server/data/zk
clientPort=2181

server.1=192.168.163.160:2888:3888
server.2=192.168.163.161:2888:3888
server.3=192.168.163.162:2888:3888

In ActiveMQ 5.10 web console you can view and delete the pending messages in a Queue