ActiveMQ集群介绍

ActiveMQ具有强大和灵活的集群功能，但在使用的过程中会发现很多的缺点，ActiveMQ的集群方式主要由两种：Master-Slave（ActiveMQ5.8版本已不可用）和Broker Cluster。

Broker集群

一个常见的场景是有多个 JMS broker ，有一个客户连接到其中一个 broker 。如果这个 broker 失效，那么客户会自动重新连接到其它的 broker 。在 ActiveMQ 中使用 failover:// 协议来实现这个功能。如果某个网络上有多个 brokers 而且客户使用静态发现（使用 Static Transport 或 Failover Transport ）或动态发现（使用 Discovery Transport ），那么客户可以容易地在某个 broker 失效的情况下切换到其它的 brokers， 下面介绍静态发现方式：
（
动态方式也同理--只是配置文件的不同:
ActiveMQ解压目录\examples\conf\activemq-dynamic-network-broker1.xml
）

首先把从官网下载的压缩包文件解压成三个文件夹！
Static-broker1的配置：
（ActiveMQ解压目录
1\examples\conf\activemq-static-network-broker1.xml）的内容全部替换到（ActiveMQ解压目
录1\conf\activemq.xml） ---默认tcp://0.0.0.0:61616
配置文件内容稍加修改如下：

<!--

    Licensed to the Apache Software Foundation (ASF) under one or more

    contributor license agreements.  See the NOTICE file distributed with

    this work for additional information regarding copyright ownership.

    The ASF licenses this file to You under the Apache License, Version 2.0

    (the "License"); you may not use this file except in compliance with

    the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software

    distributed under the License is distributed on an "AS IS" BASIS,

    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

    See the License for the specific language governing permissions and

    limitations under the License.

-->

<!--

    Create a static network of brokers

    For more information, see:

    http://activemq.apache.org/networks-of-brokers.html

    To run this example network of ActiveMQ brokers run

    $ bin/activemq console xbean:examples/conf/activemq-static-network-broker1.xml

    and

    $ bin/activemq console xbean:examples/conf/activemq-static-network-broker2.xml

    in separate consoles

 -->

<beans

  xmlns="http://www.springframework.org/schema/beans"

  xmlns:amq="http://activemq.apache.org/schema/core"

  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

  http://activemq.apache.org/camel/schema/spring http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">

    <!-- Allows us to use system properties as variables in this configuration file -->

    <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>

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

        <plugins>

            <!--  use JAAS to authenticate using the login.config file on the classpath to configure JAAS -->

            <jaasAuthenticationPlugin configuration="activemq" />

            <!--  lets configure a destination based authorization mechanism -->

            <authorizationPlugin>

                <map>

                    <authorizationMap>

                        <authorizationEntries>

                            <authorizationEntry topic=">" read="admins" write="admins" admin="admins" />

                            <authorizationEntry queue=">" read="admins" write="admins" admin="admins" />

                            <authorizationEntry topic="ActiveMQ.Advisory.>" read="admins" write="admins" admin="admins"/>

                            <authorizationEntry queue="ActiveMQ.Advisory.>" read="admins" write="admins" admin="admins"/>

                        </authorizationEntries>

                    </authorizationMap>

                </map>

            </authorizationPlugin>

        </plugins>

        <!-- Destination specific policies using destination names or wildcards -->

        <destinationPolicy>

            <policyMap>

                <policyEntries>

                    <policyEntry queue=">" producerFlowControl="true" memoryLimit="20mb">

                        <deadLetterStrategy>

                          <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true" />

                        </deadLetterStrategy>

                    </policyEntry>

                    <policyEntry topic=">" producerFlowControl="true" memoryLimit="20mb">

                    </policyEntry>

                </policyEntries>

            </policyMap>

        </destinationPolicy>

        <!-- Use the following to configure how ActiveMQ is exposed in JMX -->

        <managementContext>

            <managementContext createConnector="true" connectorPort="1102"/>

        </managementContext>

        <!--

            The store and forward broker networks ActiveMQ will listen to

            Create a duplex connector to the first broker

        -->

        <networkConnectors>

            <networkConnector userName="admin" password="admin123456" uri="static:(tcp://localhost:61618)" duplex="true"/>

        </networkConnectors>

        <persistenceAdapter>

            <kahaDB directory="${activemq.data}/static-broker2/kahadb" />

        </persistenceAdapter>

        <!--  The maximum amount of space the broker will use before slowing down producers -->

        <systemUsage>

            <systemUsage>

                <memoryUsage>

                    <memoryUsage limit="20 mb"/>

                </memoryUsage>

                <storeUsage>

                    <storeUsage limit="1 gb" name="foo"/>

                </storeUsage>

                <tempUsage>

                    <tempUsage limit="100 mb"/>

                </tempUsage>

            </systemUsage>

        </systemUsage>

        <!-- The transport connectors ActiveMQ will listen to -->

        <transportConnectors>

            <transportConnector name="openwire" uri="tcp://0.0.0.0:61616"/>

        </transportConnectors>

    </broker>

    <import resource="jetty.xml"/>

</beans>

（ActiveMQ解压目录2\examples\conf\activemq-static-network-broker1.xml）的内容全部替换 到（ActiveMQ解压目录2\conf\activemq.xml） ---默认tcp://0.0.0.0:61618
配置文件内容稍加修改如下：

<!--

    Licensed to the Apache Software Foundation (ASF) under one or more

    contributor license agreements.  See the NOTICE file distributed with

    this work for additional information regarding copyright ownership.

    The ASF licenses this file to You under the Apache License, Version 2.0

    (the "License"); you may not use this file except in compliance with

    the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software

    distributed under the License is distributed on an "AS IS" BASIS,

    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

    See the License for the specific language governing permissions and

    limitations under the License.

-->

<!--

    Create a static network of brokers

    For more information, see:

    http://activemq.apache.org/networks-of-brokers.html

    To run this example network of ActiveMQ brokers run

    $ bin/activemq console xbean:examples/conf/activemq-static-network-broker1.xml

    and

    $ bin/activemq console xbean:examples/conf/activemq-static-network-broker2.xml

    in separate consoles

 -->

<beans

  xmlns="http://www.springframework.org/schema/beans"

  xmlns:amq="http://activemq.apache.org/schema/core"

  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

  http://activemq.apache.org/camel/schema/spring http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">

    <!-- Allows us to use system properties as variables in this configuration file -->

    <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>

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

        <plugins>

            <!--  use JAAS to authenticate using the login.config file on the classpath to configure JAAS -->

            <jaasAuthenticationPlugin configuration="activemq" />

            <!--  lets configure a destination based authorization mechanism -->

            <authorizationPlugin>

                <map>

                    <authorizationMap>

                        <authorizationEntries>

                            <authorizationEntry topic=">" read="admins" write="admins" admin="admins" />

                            <authorizationEntry queue=">" read="admins" write="admins" admin="admins" />

                            <authorizationEntry topic="ActiveMQ.Advisory.>" read="admins" write="admins" admin="admins"/>

                            <authorizationEntry queue="ActiveMQ.Advisory.>" read="admins" write="admins" admin="admins"/>

                        </authorizationEntries>

                    </authorizationMap>

                </map>

            </authorizationPlugin>

        </plugins>

        <!-- Destination specific policies using destination names or wildcards -->

        <destinationPolicy>

            <policyMap>

                <policyEntries>

                    <policyEntry queue=">" producerFlowControl="true" memoryLimit="20mb">

                        <deadLetterStrategy>

                          <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true" />

                        </deadLetterStrategy>

                    </policyEntry>

                    <policyEntry topic=">" producerFlowControl="true" memoryLimit="20mb">

                    </policyEntry>

                </policyEntries>

            </policyMap>

        </destinationPolicy>

        <!-- Use the following to configure how ActiveMQ is exposed in JMX -->

        <managementContext>

            <managementContext createConnector="true" connectorPort="1102"/>

        </managementContext>

        <!--

            The store and forward broker networks ActiveMQ will listen to

            Create a duplex connector to the first broker

        -->

        <networkConnectors>

            <networkConnector userName="admin" password="admin123456" uri="static:(tcp://localhost:61620)" duplex="true"/>

        </networkConnectors>

        <persistenceAdapter>

            <kahaDB directory="${activemq.data}/static-broker2/kahadb" />

        </persistenceAdapter>

        <!--  The maximum amount of space the broker will use before slowing down producers -->

        <systemUsage>

            <systemUsage>

                <memoryUsage>

                    <memoryUsage limit="20 mb"/>

                </memoryUsage>

                <storeUsage>

                    <storeUsage limit="1 gb" name="foo"/>

                </storeUsage>

                <tempUsage>

                    <tempUsage limit="100 mb"/>

                </tempUsage>

            </systemUsage>

        </systemUsage>

        <!-- The transport connectors ActiveMQ will listen to -->

        <transportConnectors>

            <transportConnector name="openwire" uri="tcp://0.0.0.0:61618"/>

        </transportConnectors>

    </broker>

    <import resource="jetty.xml"/>

</beans>

（ActiveMQ解压目录3\examples\conf\activemq-static-network-broker1.xml）的内容全部替换 到（ActiveMQ解压目录3\conf\activemq.xml） ---默认tcp://0.0.0.0:61618
配置文件内容稍加修改如下：

<!--

    Licensed to the Apache Software Foundation (ASF) under one or more

    contributor license agreements.  See the NOTICE file distributed with

    this work for additional information regarding copyright ownership.

    The ASF licenses this file to You under the Apache License, Version 2.0

    (the "License"); you may not use this file except in compliance with

    the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

    Unless required by applicable law or agreed to in writing, software

    distributed under the License is distributed on an "AS IS" BASIS,

    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

    See the License for the specific language governing permissions and

    limitations under the License.

-->

<!--

    Create a static network of brokers

    For more information, see:

    http://activemq.apache.org/networks-of-brokers.html

    To run this example network of ActiveMQ brokers run

    $ bin/activemq console xbean:examples/conf/activemq-static-network-broker1.xml

    and

    $ bin/activemq console xbean:examples/conf/activemq-static-network-broker2.xml

    in separate consoles

 -->

<beans

  xmlns="http://www.springframework.org/schema/beans"

  xmlns:amq="http://activemq.apache.org/schema/core"

  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

  http://activemq.apache.org/camel/schema/spring http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">

    <!-- Allows us to use system properties as variables in this configuration file -->

    <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer"/>

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

        <plugins>

            <!--  use JAAS to authenticate using the login.config file on the classpath to configure JAAS -->

            <jaasAuthenticationPlugin configuration="activemq" />

            <!--  lets configure a destination based authorization mechanism -->

            <authorizationPlugin>

                <map>

                    <authorizationMap>

                        <authorizationEntries>

                            <authorizationEntry topic=">" read="admins" write="admins" admin="admins" />

                            <authorizationEntry queue=">" read="admins" write="admins" admin="admins" />

                            <authorizationEntry topic="ActiveMQ.Advisory.>" read="admins" write="admins" admin="admins"/>

                            <authorizationEntry queue="ActiveMQ.Advisory.>" read="admins" write="admins" admin="admins"/>

                        </authorizationEntries>

                    </authorizationMap>

                </map>

            </authorizationPlugin>

        </plugins>

        <!-- Destination specific policies using destination names or wildcards -->

        <destinationPolicy>

            <policyMap>

                <policyEntries>

                    <policyEntry queue=">" producerFlowControl="true" memoryLimit="20mb">

                        <deadLetterStrategy>

                          <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true" />

                        </deadLetterStrategy>

                    </policyEntry>

                    <policyEntry topic=">" producerFlowControl="true" memoryLimit="20mb">

                    </policyEntry>

                </policyEntries>

            </policyMap>

        </destinationPolicy>

        <!-- Use the following to configure how ActiveMQ is exposed in JMX -->

        <managementContext>

            <managementContext createConnector="true" connectorPort="1102"/>

        </managementContext>

        <!--

            The store and forward broker networks ActiveMQ will listen to

            Create a duplex connector to the first broker

        -->

        <networkConnectors>

            <networkConnector userName="admin" password="admin123456" uri="static:(tcp://localhost:61616)" duplex="true"/>

        </networkConnectors>

        <persistenceAdapter>

            <kahaDB directory="${activemq.data}/static-broker2/kahadb" />

        </persistenceAdapter>

        <!--  The maximum amount of space the broker will use before slowing down producers -->

        <systemUsage>

            <systemUsage>

                <memoryUsage>

                    <memoryUsage limit="20 mb"/>

                </memoryUsage>

                <storeUsage>

                    <storeUsage limit="1 gb" name="foo"/>

                </storeUsage>

                <tempUsage>

                    <tempUsage limit="100 mb"/>

                </tempUsage>

            </systemUsage>

        </systemUsage>

        <!-- The transport connectors ActiveMQ will listen to -->

        <transportConnectors>

            <transportConnector name="openwire" uri="tcp://0.0.0.0:61620"/>

        </transportConnectors>

    </broker>

    <import resource="jetty.xml"/>

</beans>

需要注意的是：由于是本地配置测试，故不能端口号相同(包括tcp和http)，如果是三台服务器上配置，那么端口可以相同。

tcp:(ActiveMQ解压目录\conf\activemq.xml)

(1).<managementContext createConnector="true" connectorPort="1102"/>
(2).<networkConnector userName="admin" password="admin123456" uri="static:(tcp://localhost:61616)" duplex="true"/>
(3).<transportConnector name="openwire" uri="tcp://0.0.0.0:61620"/>

http:(ActiveMQ解压目录\conf\jetty.xml)

<property name="port" value="8162"/>

最后分别启动这三个activemq服务！ (此处是windows7 64位系统)
（ActiveMQ解压目录1\bin\win64\activemq.bat）
（ActiveMQ解压目录2\bin\win64\activemq.bat）
（ActiveMQ解压目录3\bin\win64\activemq.bat）

测试：先启动消费者！然后启动生产者发送消息。(至于消费者和生产者代码，请留意我的另一篇博文activemq整合spring)
先测试两个服务同时启动情况，然后把其中一个服务关闭保留一个再测试。（点对点 一对多也进行测试）

ActiveMQ-5.13.0集群的更多相关文章

  1. apache-kylin-2.5.2-bin-cdh57与cdh-5.13.0集群整合运用

    1.下载kylin最新版apache-kylin-2.5.2-bin-cdh57: 2.解压配置环境变量: export BASE_PATH="/opt/cloudera/parcels/C ...

  2. 在Hadoop-2.2.0集群上安装 Hive-0.13.1 with MySQL

    fesh个人实践,欢迎经验交流!本文Blog地址:http://www.cnblogs.com/fesh/p/3872872.html 软件环境 操作系统:Ubuntu14.04 JDK版本:jdk1 ...

  3. 关于ActiveMQ的几种集群配置

    ActiveMQ的几种集群配置. Queue consumer clusters 此集群让多个消费者同时消费一个队列,若某个消费者出问题无法消费信息,则未消费掉的消息将被发给其他正常的消费者,结构图如 ...

  4. ActiveMQ的几种集群配置

    ActiveMQ是一款功能强大的消息服务器,它支持许多种开发语言,例如Java, C, C++, C#等等.企业级消息服务器无论对服务器稳定性还是速度,要求都很高,而ActiveMQ的分布式集群则能很 ...

  5. activemq+Zookeper高可用集群方案配置

    在高并发.对稳定性要求极高的系统中,高可用的是必不可少的,当然ActiveMQ也有自己的集群方案.从ActiveMQ 5.9开始,ActiveMQ的集群实现方式取消了传统的Master-Slave方式 ...

  6. Ubuntu 12.04下spark1.0.0 集群搭建（原创）

    spark1.0.0新版本的于2014-05-30正式发布啦,新的spark版本带来了很多新的特性,提供了更好的API支持,spark1.0.0增加了Spark SQL组件,增强了标准库(ML.str ...

  7. hadoop-2.6.0集群开发环境配置

    hadoop-2.6.0集群开发环境配置 一．环境说明 1.1安装环境说明 本例中,操作系统为CentOS 6.6, JDK版本号为JDK 1.7,Hadoop版本号为Apache Hadoop 2. ...

  8. centos7.4安装高可用(haproxy+keepalived实现)kubernetes1.6.0集群（开启TLS认证）

    目录 目录 前言 集群详情 环境说明 安装前准备 提醒 一.创建TLS证书和秘钥 安装CFSSL 创建 CA (Certificate Authority) 创建 CA 配置文件 创建 CA 证书签名 ...

  9. Spring Cloud Alibaba(7)---docker-compose搭建nacos1.4.0集群

    docker-compose搭建nacos1.4.0集群 有关Nacos之前写过四篇文章. Spring Cloud Alibaba(3)---Nacos概述 Spring Cloud Alibaba ...

随机推荐

  1. mongoose中给字段添加索引的方法

    mongoose中给字段添加索引的方法有两种,一种通过在定义schema的时候配置,如: var animalSchema = new Schema({ name: String, type: Str ...

  2. python学习之pyc，pyo，pyd文件

    pyc:二进制文件,python文件经过编译器编译之后的文件.可以提高文件加载速度. pyo:二进制文件,优化编译后的文件.可以通过`python -O file.py`生成. pyd:python的 ...

  3. mysql：索引原理与慢查询优化

    一 索引的原理 1. 索引原理 索引的目的在于提高查询效率,与我们查阅图书所用的目录是一个道理:先定位到章,然后定位到该章下的一个小节,然后找到页数.相似的例子还有:查字典,查火车车次,飞机航班等 本 ...

  4. Python中if __name__ == '__main__':作用

    #hello.pydef sayHello(): str="hello" print(str); if__name__=="__main__": print ( ...

  5. 使用Konva创建进度条

    <!doctype html> <html lang="en"> <head> <meta charset="UTF-8&quo ...

  6. jquery50个代码段

    1. 如何创建嵌套的过滤器 ? 1 //允许你减少集合中的匹配元素的过滤器, //只剩下那些与给定的选择器匹配的部分.在这种情况下, //查询删除了任何没(:not)有(:has) //包含class ...

  7. C#通过“委托和事件”的方式实现进程监控并与“普通方式”对比

    今天重新学习了一下观察者模式,对我的思路产生了启发.进程监控程序之前写过几个,这回换一种思路,改用委托和事件来实现.我已经用序号将关键的几步标注,方便大家理顺思路.代码如下: using System ...

  8. 使用Supervisor管理Linux进程

    使用Supervisor管理Linux进程 简介 Supervisor是一个C/S系统,它可以在类UNIX系统上控制系统进程,由python编写,提供了大量的功能来实现对进程的管理. 安装 sudo ...

  9. multi-mechanize error: can not find test script: v_user.py问题

    从github上下载,安装multi-mechanize,新建工程,运行工程报错. 环境: win7-x64, python 2.7 multi-mechanize can not find test ...

  10. 人工智能时代,应立即学习python

    人工智能时代,应立即学习python 应用:web开发,自动化运维开发,自动化测试,数据分析,机器学习 1.python 快速易学习2.python 基于web开发(zhihu:tornad web框 ...