如何解决Apache Artemis-保留消息在对称集群上不相同
使用带有MQTT协议的Artemis 2.12
我在对称集群中设置了两个代理A和B。在每个代理上，有一个与代理A连接的生产者Pa和与代理B相连的Pb。另外，在每个代理上，有一个订阅主题foo的消费者，Ca与代理A相连，Cb与代理B相连。
当生产者Pa将关于主题foo的保留消息（retainedMessagePa）发布给代理A时，Ca和Cb均获得消息（retainedMessagePa）。如果Ca断开连接，并使用干净的会话重新连接到Broker A，它将获得相同的保留消息（retainedMessagePa）。但是，如果Cb断开连接并通过与代理B的干净会话重新连接，则它不会获得保留的消息。同样，如果生产者Pb将有关主题foo的保留消息发布到代理B（retainedMessagePb），如果Ca和Cb都连接到它们的代理，它们将获得相同的保留消息（retainedMessagePb）。但是，当其中一个重新连接到干净的会话时，它们将得到最后保留的消息发送给其代理。 Ca接收（retainedMessagePab），Cb接收（retainedMessagePb）
如何配置2个代理具有相同的保留消息？
<configuration xmlns="urn:activemq"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
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>BrokerA</name> <!-- Changed on each Broker -->
<persistence-enabled>true</persistence-enabled>
<journal-type>NIO</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>-1</journal-pool-files>
<journal-buffer-size>10485760</journal-buffer-size>
<journal-buffer-timeout>1308000</journal-buffer-timeout>
<disk-scan-period>5000</disk-scan-period>
<max-disk-usage>95</max-disk-usage>
<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>
<acceptors>
<acceptor name="artemis">tcp://0.0.0.0:61616</acceptor>
<acceptor name="mqtt">tcp://0.0.0.0:1883?tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=MQTT;useEpoll=true</acceptor>
</acceptors>
<connectors>
<connector name="L1">tcp://BrokerA:61616</connector>
<connector name="L2">tcp://BrokerB:61616</connector>
</connectors>
<cluster-connections>
<cluster-connection name="cluster">
<address>#</address>
<connector-ref>L1</connector-ref> <!-- Changed on each Broker -->
<retry-interval>1000</retry-interval>
<reconnect-attempts>-1</reconnect-attempts>
<message-load-balancing>ON_DEMAND</message-load-balancing>
<max-hops>1</max-hops>
<static-connectors>
<connector-ref>L2</connector-ref> <!-- Changed on each Broker -->
</static-connectors>
</cluster-connection>
</cluster-connections>
<cluster-user>admin</cluster-user>
<cluster-password>admin</cluster-password>
<security-settings>
<security-setting match="#">
<permission type="createNonDurableQueue" roles="admin"/>
<permission type="deleteNonDurableQueue" roles="admin"/>
<permission type="createDurableQueue" roles="admin"/>
<permission type="deleteDurableQueue" roles="admin"/>
<permission type="createAddress" roles="admin"/>
<permission type="deleteAddress" roles="admin"/>
<permission type="consume" roles="admin"/>
<permission type="browse" roles="admin"/>
<permission type="send" roles="admin"/>
<!-- we need this otherwise ./artemis data imp wouldn't work -->
<permission type="manage" roles="admin"/>
</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>
</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>
</address-setting>
</address-settings>
<addresses>
<address name="DLQ">
<anycast>
<queue name="DLQ" />
</anycast>
</address>
<address name="ExpiryQueue">
<anycast>
<queue name="ExpiryQueue" />
</anycast>
</address>
</addresses>
</core>
</configuration>
我尝试将<redistribution-delay>0</redistribution-delay>设置为<message-load-balancing>ON_DEMAND</message-load-balancing>对此没有帮助。
我还尝试了<message-load-balancing>STRICT</message-load-balancing>，该方法也无济于事。
版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 dio@foxmail.com 举报，一经查实，本站将立刻删除。
