activitymq 集群构建

测试zk是否正常

[root@node2 bin]# cd /zk/1/zookeeper-3.4.10/bin/
[root@node2 bin]#  ./zkCli.sh -server 10.50.50.38:2181
Connecting to 10.50.50.38:2181
2018-12-03 16:03:09,869 [myid:] - INFO  [main:Environment@100] - Client environment:zookeeper.version=3.4.10-39d3a4f269333c922ed3db283be479f9deacaa0f, built on 03/23/2017 10:13 GMT
2018-12-03 16:03:09,873 [myid:] - INFO  [main:Environment@100] - Client environment:host.name=node2
2018-12-03 16:03:09,873 [myid:] - INFO  [main:Environment@100] - Client environment:java.version=1.8.0_171
2018-12-03 16:03:09,876 [myid:] - INFO  [main:Environment@100] - Client environment:java.vendor=Oracle Corporation
2018-12-03 16:03:09,876 [myid:] - INFO  [main:Environment@100] - Client environment:java.home=/usr/java/jdk1.8.0_171-amd64/jre2018-12-03 16:03:09,877 [myid:] - INFO  [main:Environment@100] - Client environment:java.io.tmpdir=/tmp
2018-12-03 16:03:09,877 [myid:] - INFO  [main:Environment@100] - Client environment:java.compiler=<NA>
2018-12-03 16:03:09,877 [myid:] - INFO  [main:Environment@100] - Client environment:os.name=Linux
2018-12-03 16:03:09,877 [myid:] - INFO  [main:Environment@100] - Client environment:os.arch=amd64
2018-12-03 16:03:09,877 [myid:] - INFO  [main:Environment@100] - Client environment:os.version=3.10.0-862.el7.x86_64
2018-12-03 16:03:09,877 [myid:] - INFO  [main:Environment@100] - Client environment:user.name=root
2018-12-03 16:03:09,877 [myid:] - INFO  [main:Environment@100] - Client environment:user.home=/root
2018-12-03 16:03:09,877 [myid:] - INFO  [main:Environment@100] - Client environment:user.dir=/zk/1/zookeeper-3.4.10/bin
2018-12-03 16:03:09,879 [myid:] - INFO  [main:ZooKeeper@438] - Initiating client connection, connectString=10.50.50.38:2181 sessionTimeout=30000 watcher=org.apache.zookeeper.ZooKeeperMain$MyW
atcher@799f7e29Welcome to ZooKeeper!
2018-12-03 16:03:09,905 [myid:] - INFO  [main-SendThread(10.50.50.38:2181):ClientCnxn$SendThread@1032] - Opening socket connection to server 10.50.50.38/10.50.50.38:2181. Will not attempt to
authenticate using SASL (unknown error)JLine support is enabled
2018-12-03 16:03:09,982 [myid:] - INFO  [main-SendThread(10.50.50.38:2181):ClientCnxn$SendThread@876] - Socket connection established to 10.50.50.38/10.50.50.38:2181, initiating session
2018-12-03 16:03:09,997 [myid:] - INFO  [main-SendThread(10.50.50.38:2181):ClientCnxn$SendThread@1299] - Session establishment complete on server 10.50.50.38/10.50.50.38:2181, sessionid = 0x1
6772dd90850001, negotiated timeout = 30000
WATCHER::WatchedEvent state:SyncConnected type:None path:null
[zk: 10.50.50.38:2181(CONNECTED) 0]

　下载配置启动

mkdir -pv /activemq/activemq{1,2,3}
tar xf apache-activemq-5.14.3-bin.tar.gz -C /activemq/activemq1/
tar xf apache-activemq-5.14.3-bin.tar.gz -C /activemq/activemq2/
tar xf apache-activemq-5.14.3-bin.tar.gz -C /activemq/activemq3/
cd /activemq/activemq1/apache-activemq-5.14.3/conf/
cp -a activemq.xml{,.bak}
后面需要修改的配置文件都在ACTIVEMQ_HOME/conf文件夹下。首先修改每个ActiveMQ的持久化方式（修改ACTIVEMQ_HOME/bin/activemq.xml文件），ActiveMQ默认使用的是kahaDB作为持久化存储数据的，这里修改成levelDB。如下所示
vim activemq.xml<persistenceAdapter><replicatedLevelDB directory="${activemq.data}/leveldb"replicas="3"bind="tcp://0.0.0.0:62621"zkAddress="10.50.50.38:2381,10.50.50.38:2381,10.50.50.38:2381"hostname="10.50.50.38" zkPath="/activemq/leveldb-stores" /></persistenceAdapter>
[root@node2 conf]# cd /activemq/activemq2/apache-activemq-5.15.8/conf/
[root@node2 conf]# vim activemq.xmlmechanism is the KahaDB store (identified by the kahaDB tag).For more information, see:http://activemq.apache.org/persistence.html--><persistenceAdapter><replicatedLevelDB directory="${activemq.data}/leveldb"replicas="3"bind="tcp://0.0.0.0:62621"zkAddress="10.50.50.38:2381,10.50.50.38:2381,10.50.50.38:2381"hostname="10.50.50.38" zkPath="/activemq/leveldb-stores" /></persistenceAdapter><transportConnectors><!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB --><transportConnector name="openwire" uri="tcp://0.0.0.0:61617?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>  把端口改61617<transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/><transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/><transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/><transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/></transportConnectors>
[root@node2 conf]# vim jetty.xml <bean id="contexts" class="org.eclipse.jetty.server.handler.ContextHandlerCollection"></bean><bean id="jettyPort" class="org.apache.activemq.web.WebConsolePort" init-method="start"><!-- the default port number for the web console --><property name="host" value="0.0.0.0"/><property name="port" value="8162"/>  修改默认端口</bean>
[root@node2 conf]# cd /activemq/activemq3/apache-activemq-5.15.8/conf/
[root@node2 conf]# vim activemq.xml
[root@node2 conf]# vim activemq.xml<persistenceAdapter><replicatedLevelDB directory="${activemq.data}/leveldb"replicas="3"bind="tcp://0.0.0.0:62621"zkAddress="10.50.50.38:2381,10.50.50.38:2381,10.50.50.38:2381"hostname="10.50.50.38" zkPath="/activemq/leveldb-stores" /></persistenceAdapter><transportConnectors><!-- DOS protection, limit concurrent connections to 1000 and frame size to 100MB --><transportConnector name="openwire" uri="tcp://0.0.0.0:61618?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>  默认端口修改<transportConnector name="amqp" uri="amqp://0.0.0.0:5672?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/><transportConnector name="stomp" uri="stomp://0.0.0.0:61613?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/><transportConnector name="mqtt" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/><transportConnector name="ws" uri="ws://0.0.0.0:61614?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>[root@node2 conf]# vim jetty.xml </tran    <bean id="jettyPort" class="org.apache.activemq.web.WebConsolePort" init-method="start"><!-- the default port number for the web console --><property name="host" value="0.0.0.0"/><property name="port" value="8163"/>  修改默认端口</bean>
sportConnectors>

启动服务

[root@node2 conf]# cd /activemq/activemq1/apache-activemq-5.15.8/bin/
[root@node2 bin]# ./activemq start
[root@node2 bin]#cd /activemq/activemq2/apache-activemq-5.15.8/bin/
[root@node2 bin]# ./activemq start
[root@node2 bin]#cd /activemq/activemq3/apache-activemq-5.15.8/bin/
[root@node2 bin]# ./activemq start
[root@node2 bin]# ss -lntp | grep 61616
LISTEN     0      128         :::61616                   :::*                   users:(("java",pid=13674,fd=154))

　参考文章：https://blog.csdn.net/haoyuyang/article/details/53931710

转载于:https://www.cnblogs.com/rdchenxi/p/10059353.html

activitymq 集群构建相关推荐

KubeSphere——KubeSphere集群构建实战
摘要 KubeSphere 愿景是打造一个以 Kubernetes 为内核的云原生分布式操作系统,它的架构可以非常方便地使第三方应用与云原生生态组件进行即插即用(plug-and-play)的集成,支 ...
Docker——docker-registry私有仓库集群构建
摘要随着docker使用的镜像越来越多,就需要有一个保存镜像的地方,这就是仓库.目前常用的两种仓库:公共仓库和私有仓库.最方便的就是使用公共仓库上传和下载,下载公共仓库的镜像是不需要注册的,但是上传 ...
kubernetes入门到精通（一）：内容编排与k8s介绍，集群构建教程，如何开启dashboard
集群环境容器部署的困境怎么分配这 10 台服务器?2 万台呢? 容器编排工具 docker compose,单机容器编排工具 docker swam 跨主机的,集群容器编排工具 kubernetes ...
Orleans的集群构建
听闻一周前,微软公布了.net core2.0,以及各种各样的其他core2.0.大家都很兴奋.微妈的诚意真是满满的.这次开源势头让我感觉到了微妈的技术实力之雄厚.我在这里祝福C#越来越好.细心的人似 ...
基于YARN集群构建运行PySpark Application
文章转载:https://www.tuicool.com/articles/eaYVN3v Spark Application可以直接运行在YARN集群上,这种运行模式,会将资源的管理与协调统一交给Y ...
[k8s]jenkins配合kubernetes插件实现k8s集群构建的持续集成
另一个结合harbor自动构建镜像的思路: 即code+baseimage一体的方案 - 程序员将代码提交到代码仓库gitlab - 钩子触发jenkins master启动一次构建 - jenkin ...
02.es的节点发现和集群构建
文章目录 1. 简介 2. 节点发现 3. 多数生效的操作 4. 投票人信息设置 1. Voting configurations 中的节点信息 2. Voting configurations 为何 ...
mongodb 集群shard_mongodb集群构建方案（二）
0.创建网段 docker network create mongo 1.编写yaml文件,,这里我命名fates-mongo-compose.yaml 以下这个文件,建立3个mongo shard服 ...
MongoDB集群构建
最近做的项目,拿出来分享交流. 六台主机 hostname分别为wens012~017 IP:10.50.9.12~10.50.9.17 下面为部署方案六个server,每个server上跑四个进程 ...
Docker 中的网络管理与集群构建
Docker中的网络与数据管理一.Docker网络管理 1.Docker默认网络管理 docker的网络模式注:docker有三种网络模式,默认的为bridge,配置后可以和宿主机通信,host和 ...

activitymq 集群构建

activitymq 集群构建相关推荐

最新文章

热门文章