在本地运行ActiveMQ Artemis时，我可以使用相同的ConnectionFactory连接两个不同的队列。
当我尝试连接到客户端的ActiveMQ时，一次只能保持一个消费者处于活动状态。对于其他的我不断得到：
Could not refresh JMS Connection for destination 'QUEUE_NAME' - retrying using FixedBackOff{interval=5000, currentAttempts=27, maxAttempts=unlimited}.
Cause: Failed to create session factory; nested exception is
ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.]
与我的客户核实后，他告诉我在阿耳emi弥斯的日志上，他只是看到一堆
2019-02-06 16:44:44,725 ERROR [org.apache.activemq.artemis.core.server] AMQ224088: Timeout (10 seconds) while handshaking has occurred.
2019-02-06 16:44:54,595 ERROR [org.apache.activemq.artemis.core.server] AMQ224088: Timeout (10 seconds) while handshaking has occurred.
2019-02-06 16:45:04,670 ERROR [org.apache.activemq.artemis.core.server] AMQ224088: Timeout (10 seconds) while handshaking has occurred.
2019-02-06 16:45:54,595 ERROR [org.apache.activemq.artemis.core.server] AMQ224088: Timeout (10 seconds) while handshaking has occurred.
2019-02-06 16:46:04,655 ERROR [org.apache.activemq.artemis.core.server] AMQ224088: Timeout (10 seconds) while handshaking has occurred.
现在，如果我为每个队列使用完全相同的参数创建不同的ConnectionFactory，则可以同时连接它们。
我基本上是在使用spring-boot-artemis（很像this教程），但是我不认为这与我的代码有关，但与ActiveMQ有关（因为它可以在本地与我的ActiveMQ Artemis一起使用）。 / p>
据我所知，我的客户未在其ActiveMQ Artemis上进行任何配置。这只是默认安装。他的ActiveMQ正在被其他应用程序使用，我怀疑这可能会导致连接工厂出现某种形式的饥饿……？关于如何调试或了解此方法的任何想法？
谢谢！
修改
我得到了broker.xml，并删除了所有客户数据以发布到此处。我要连接的队列在NAME3.#规则的security-settings匹配规则下，我使用my_user用户连接到该队列：
<?xml version='1.0'?>
<!--
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.
-->
<configuration
xmlns="urn:activemq"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xi="http://www.w3.org/2001/XInclude"
xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd">
<core
xmlns="urn:activemq:core"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:activemq:core ">
<name>DEV</name>
<persistence-enabled>true</persistence-enabled>
<!-- this could be ASYNCIO, MAPPED, NIO
ASYNCIO: Linux Libaio
MAPPED: mmap files
NIO: Plain Java Files
-->
<journal-type>ASYNCIO</journal-type>
<paging-directory>data/paging</paging-directory>
<bindings-directory>data/bindings</bindings-directory>
<journal-directory>data/journal</journal-directory>
<large-messages-directory>data/large-messages</large-messages-directory>
<journal-datasync>true</journal-datasync>
<journal-min-files>2</journal-min-files>
<journal-pool-files>10</journal-pool-files>
<journal-file-size>10M</journal-file-size>
<jmx-management-enabled>true</jmx-management-enabled>
<async-connection-execution-enabled>false</async-connection-execution-enabled>
<!--
This value was determined through a calculation.
Your system could perform 3.85 writes per millisecond
on the current journal configuration.
That translates as a sync write every 260000 nanoseconds.
Note: If you specify 0 the system will perform writes directly to the disk.
We recommend this to be 0 if you are using journalType=MAPPED and ournal-datasync=false.
-->
<journal-buffer-timeout>260000</journal-buffer-timeout>
<journal-buffer-size>1000000</journal-buffer-size>
<!--
When using ASYNCIO, this will determine the writing queue depth for libaio.
-->
<journal-max-io>4096</journal-max-io>
<!--
You can verify the network health of a particular NIC by specifying the <network-check-NIC> element.
<network-check-NIC>theNicName</network-check-NIC>
-->
<!--
Use this to use an HTTP server to validate the network
<network-check-URL-list>http://www.apache.org</network-check-URL-list> -->
<!-- <network-check-period>10000</network-check-period> -->
<!-- <network-check-timeout>1000</network-check-timeout> -->
<!-- this is a comma separated list, no spaces, just DNS or IPs
it should accept IPV6
Warning: Make sure you understand your network topology as this is meant to validate if your network is valid.
Using IPs that could eventually disappear or be partially visible may defeat the purpose.
You can use a list of multiple IPs, and if any successful ping will make the server OK to continue running -->
<!-- <network-check-list>10.0.0.1</network-check-list> -->
<!-- use this to customize the ping used for ipv4 addresses -->
<!-- <network-check-ping-command>ping -c 1 -t %d %s</network-check-ping-command> -->
<!-- use this to customize the ping used for ipv6 addresses -->
<!-- <network-check-ping6-command>ping6 -c 1 %2$s</network-check-ping6-command> -->
<!-- how often we are looking for how many bytes are being used on the disk in ms -->
<disk-scan-period>5000</disk-scan-period>
<!-- once the disk hits this limit the system will block, or close the connection in certain protocols
that won't support flow control. -->
<max-disk-usage>90</max-disk-usage>
<!-- should the broker detect dead locks and other issues -->
<critical-analyzer>true</critical-analyzer>
<critical-analyzer-timeout>120000</critical-analyzer-timeout>
<critical-analyzer-check-period>60000</critical-analyzer-check-period>
<critical-analyzer-policy>HALT</critical-analyzer-policy>
<!-- the system will enter into page mode once you hit this limit.
This is an estimate in bytes of how much the messages are using in memory
The system will use half of the available memory (-Xmx) by default for the global-max-size.
You may specify a different value here if you need to customize it to your needs.
<global-max-size>100Mb</global-max-size>
-->
<acceptors>
<!-- useEpoll means: it will use Netty epoll if you are on a system (Linux) that supports it -->
<!-- amqpCredits: The number of credits sent to AMQP producers -->
<!-- amqpLowCredits: The server will send the # credits specified at amqpCredits at this low mark -->
<!-- Note: If an acceptor needs to be compatible with HornetQ and/or Artemis 1.x clients add
"anycastPrefix=jms.queue.;multicastPrefix=jms.topic." to the acceptor url.
See https://issues.apache.org/jira/browse/ARTEMIS-1644 for more information. -->
<!-- Acceptor for every supported protocol -->
<acceptor name="openwire">tcp://0.0.0.0:61616?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;connectionTtl=60000;protocols=CORE,AMQP,STOMP,HORNETQ,MQTT,OPENWIRE;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;needClientAuth=true;sslEnabled=false;anycastPrefix=jms.queue.;multicastPrefix=jms.topic.</acceptor>
<!-- AMQP Acceptor. Listens on default AMQP port for AMQP traffic.-->
<acceptor name="amqp">tcp://0.0.0.0:5672?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpMinCredits=300</acceptor>
<!-- STOMP Acceptor. -->
<acceptor name="stomp">tcp://0.0.0.0:61613?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;connectionTtl=60000;protocols=STOMP;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;needClientAuth=true;sslEnabled=false;anycastPrefix=jms.queue.;multicastPrefix=jms.topic.</acceptor>
<!-- HornetQ Compatibility Acceptor. Enables HornetQ Core and STOMP for legacy HornetQ clients. -->
<!--acceptor name="hornetq">tcp://0.0.0.0:5445?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.;protocols=HORNETQ,STOMP;useEpoll=true</acceptor-->
<!-- MQTT Acceptor -->
<acceptor name="mqtt">tcp://0.0.0.0:1883?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true;needClientAuth=true</acceptor>
<!-- Netty Acceptor -->
<acceptor name="netty">tcp://localhost:61617?needClientAuth=true;protocols=OPENWIRE,CORE,AMQP,JMS;connectionTtl=60000;;anycastPrefix=jms.queue.;multicastPrefix=jms.topic.</acceptor>
</acceptors>
<connectors>
<connector name="netty-connector">tcp://localhost:61617</connector>
<connector name="itot-remote-connector">tcp://ip.ip.ip.ip:61616</connector>
</connectors>
<ha-policy>
<replication>
<colocated/>
</replication>
</ha-policy>
<!-- Clustering configuration -->
<broadcast-groups>
<broadcast-group name="my-broadcast-group">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<broadcast-period>10000</broadcast-period>
<connector-ref>netty-connector</connector-ref>
</broadcast-group>
</broadcast-groups>
<discovery-groups>
<discovery-group name="my-discovery-group">
<group-address>231.7.7.7</group-address>
<group-port>9876</group-port>
<refresh-timeout>10000</refresh-timeout>
</discovery-group>
</discovery-groups>
<cluster-connections>
<cluster-connection name="my-cluster">
<connector-ref>netty-connector</connector-ref>
<retry-interval>10000</retry-interval>
<use-duplicate-detection>true</use-duplicate-detection>
<message-load-balancing>STRICT</message-load-balancing>
<max-hops>1</max-hops>
<discovery-group-ref discovery-group-name="my-discovery-group"/>
</cluster-connection>
</cluster-connections>
<security-settings>
<security-setting match="#">
<permission type="createNonDurableQueue" roles="admin,amq"/>
<permission type="deleteNonDurableQueue" roles="admin,amq"/>
<permission type="createDurableQueue" roles="admin,amq"/>
<permission type="deleteDurableQueue" roles="admin,amq"/>
<permission type="createAddress" roles="admin,amq"/>
<permission type="deleteAddress" roles="admin,amq"/>
<permission type="consume" roles="admin,amq,guest"/>
<permission type="browse" roles="admin,amq,guest,read"/>
<permission type="send" roles="admin,amq"/>
<!-- we need this otherwise ./artemis data imp wouldn't work-->
<permission type="manage" roles="admin,amq,read"/>
</security-setting>
<security-setting match="NAME1.#">
<permission type="createNonDurableQueue" roles="admin,amq"/>
<permission type="deleteNonDurableQueue" roles="admin,amq"/>
<permission type="createDurableQueue" roles="admin,amq"/>
<permission type="deleteDurableQueue" roles="admin,amq"/>
<permission type="createAddress" roles="admin,amq"/>
<permission type="deleteAddress" roles="admin,amq"/>
<permission type="consume" roles="admin,amq,guest,vinspec"/>
<permission type="browse" roles="admin,amq,guest,read,vinspec"/>
<permission type="send" roles="admin,amq,vinspec"/>
<!-- we need this otherwise ./artemis data imp wouldn't work-->
<permission type="manage" roles="admin,amq,read"/>
</security-setting>
<security-setting match="NAME2.#">
<permission type="createNonDurableQueue" roles="admin,amq"/>
<permission type="deleteNonDurableQueue" roles="admin,amq"/>
<permission type="createDurableQueue" roles="admin,amq"/>
<permission type="deleteDurableQueue" roles="admin,amq"/>
<permission type="createAddress" roles="admin,amq"/>
<permission type="deleteAddress" roles="admin,amq"/>
<permission type="consume" roles="admin,amq,guest,other_user,another_user,my_user"/>
<permission type="browse" roles="admin,amq,guest,read,other_user,another_user,my_user"/>
<permission type="send" roles="admin,amq,other_user,my_user"/>
<!-- we need this otherwise ./artemis data imp wouldn't work-->
<permission type="manage" roles="admin,amq,read"/>
</security-setting>
<security-setting match="NAME3.#">
<permission type="createNonDurableQueue" roles="admin,amq"/>
<permission type="deleteNonDurableQueue" roles="admin,amq"/>
<permission type="createDurableQueue" roles="admin,amq"/>
<permission type="deleteDurableQueue" roles="admin,amq"/>
<permission type="createAddress" roles="admin,amq"/>
<permission type="deleteAddress" roles="admin,amq"/>
<permission type="consume" roles="admin,amq,guest,other_user,my_user"/>
<permission type="browse" roles="admin,amq,guest,read,other_user,my_user"/>
<permission type="send" roles="admin,amq,other_user,my_user"/>
<permission type="manage" roles="admin,amq,read"/>
</security-setting>
<security-setting match="NAME4.#">
<permission type="createNonDurableQueue" roles="admin,amq"/>
<permission type="deleteNonDurableQueue" roles="admin,amq"/>
<permission type="createDurableQueue" roles="admin,amq"/>
<permission type="deleteDurableQueue" roles="admin,amq"/>
<permission type="createAddress" roles="admin,amq"/>
<permission type="deleteAddress" roles="admin,amq"/>
<permission type="consume" roles="admin,amq,guest,other_user,another_user"/>
<permission type="browse" roles="admin,amq,guest,read,other_user,another_user"/>
<permission type="send" roles="admin,amq,other_user"/>
<!-- we need this otherwise ./artemis data imp wouldn't work-->
<permission type="manage" roles="admin,amq,read"/>
</security-setting>
<security-setting match="NAME5">
<permission type="createNonDurableQueue" roles="admin,amq"/>
<permission type="deleteNonDurableQueue" roles="admin,amq"/>
<permission type="createDurableQueue" roles="admin,amq"/>
<permission type="deleteDurableQueue" roles="admin,amq"/>
<permission type="createAddress" roles="admin,amq"/>
<permission type="deleteAddress" roles="admin,amq"/>
<permission type="consume" roles="admin,amq,guest,another_user"/>
<permission type="browse" roles="admin,amq,guest,read,another_user"/>
<permission type="send" roles="admin,amq,another_user"/>
<!-- we need this otherwise ./artemis data imp wouldn't work-->
<permission type="manage" roles="admin,amq,read"/>
</security-setting>
<security-setting match="NAME6">
<permission type="createNonDurableQueue" roles="admin,amq"/>
<permission type="deleteNonDurableQueue" roles="admin,amq"/>
<permission type="createDurableQueue" roles="admin,amq"/>
<permission type="deleteDurableQueue" roles="admin,amq"/>
<permission type="createAddress" roles="admin,amq"/>
<permission type="deleteAddress" roles="admin,amq"/>
<permission type="consume" roles="admin,amq,guest"/>
<permission type="browse" roles="admin,amq,guest,read"/>
<permission type="send" roles="admin,amq"/>
<!-- we need this otherwise ./artemis data imp wouldn't work-->
<permission type="manage" roles="admin,amq,read"/>
</security-setting>
<security-setting match="NAME7.#">
<permission type="createNonDurableQueue" roles="admin,amq"/>
<permission type="deleteNonDurableQueue" roles="admin,amq"/>
<permission type="createDurableQueue" roles="admin,amq"/>
<permission type="deleteDurableQueue" roles="admin,amq"/>
<permission type="createAddress" roles="admin,amq"/>
<permission type="deleteAddress" roles="admin,amq"/>
<permission type="consume" roles="admin,amq,guest"/>
<permission type="browse" roles="admin,amq,guest,read"/>
<permission type="send" roles="admin,amq"/>
<!-- we need this otherwise ./artemis data imp wouldn't work-->
<permission type="manage" roles="admin,amq,read"/>
</security-setting>
<security-setting match="NAME8">
<permission type="createNonDurableQueue" roles="admin,amq"/>
<permission type="deleteNonDurableQueue" roles="admin,amq"/>
<permission type="createDurableQueue" roles="admin,amq"/>
<permission type="deleteDurableQueue" roles="admin,amq"/>
<permission type="createAddress" roles="admin,amq"/>
<permission type="deleteAddress" roles="admin,amq"/>
<permission type="consume" roles="admin,amq,guest"/>
<permission type="browse" roles="admin,amq,guest,read"/>
<permission type="send" roles="admin,amq"/>
<!-- we need this otherwise ./artemis data imp wouldn't work-->
<permission type="manage" roles="admin,amq,read"/>
</security-setting>
<security-setting match="NAME9.#">
<permission type="createNonDurableQueue" roles="admin,amq"/>
<permission type="deleteNonDurableQueue" roles="admin,amq"/>
<permission type="createDurableQueue" roles="admin,amq"/>
<permission type="deleteDurableQueue" roles="admin,amq"/>
<permission type="createAddress" roles="admin,amq"/>
<permission type="deleteAddress" roles="admin,amq"/>
<permission type="consume" roles="admin,amq,guest,my_user"/>
<permission type="browse" roles="admin,amq,guest,read,my_user"/>
<permission type="send" roles="admin,amq,my_user"/>
<!-- we need this otherwise ./artemis data imp wouldn't work-->
<permission type="manage" roles="admin,amq,read"/>
</security-setting>
</security-settings>
<address-settings>
<!-- if you define auto-create on certain queues, management has to be auto-create -->
<address-setting match="activemq.management#">
<dead-letter-address>DLQ</dead-letter-address>
<expiry-address>ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<!-- with -1 only the global-max-size is in use for limiting -->
<max-size-bytes>-1</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>PAGE</address-full-policy>
<auto-create-queues>true</auto-create-queues>
<auto-create-addresses>true</auto-create-addresses>
<auto-create-jms-queues>true</auto-create-jms-queues>
<auto-create-jms-topics>true</auto-create-jms-topics>
<default-address-routing-type>ANYCAST</default-address-routing-type>
</address-setting>
<!--default for catch all-->
<address-setting match="#">
<dead-letter-address>DLQ</dead-letter-address>
<expiry-address>ExpiryQueue</expiry-address>
<redelivery-delay>0</redelivery-delay>
<!-- with -1 only the global-max-size is in use for limiting -->
<max-size-bytes>-1</max-size-bytes>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
<address-full-policy>PAGE</address-full-policy>
<auto-create-queues>true</auto-create-queues>
<auto-create-addresses>true</auto-create-addresses>
<auto-create-jms-queues>true</auto-create-jms-queues>
<auto-create-jms-topics>true</auto-create-jms-topics>
<default-address-routing-type>ANYCAST</default-address-routing-type>
</address-setting>
</address-settings>
<addresses>
<address name="DLQ">
<anycast>
<queue name="DLQ" />
</anycast>
</address>
<address name="ExpiryQueue">
<anycast>
<queue name="ExpiryQueue" />
</anycast>
</address>
</addresses>
<!-- Uncomment the following if you want to use the Standard LoggingActiveMQServerPlugin pluging to log in events -->
<broker-plugins>
<broker-plugin class-name="org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin">
<property key="LOG_ALL_EVENTS" value="true"/>
<property key="LOG_CONNECTION_EVENTS" value="true"/>
<property key="LOG_SESSION_EVENTS" value="true"/>
<property key="LOG_CONSUMER_EVENTS" value="true"/>
<property key="LOG_DELIVERING_EVENTS" value="true"/>
<property key="LOG_SENDING_EVENTS" value="true"/>
<property key="LOG_INTERNAL_EVENTS" value="true"/>
</broker-plugin>
</broker-plugins>
</core>
</configuration>