activemq NoB：代理在重新连接后未收到消息
我们有一个中心辐射型网络拓扑，其中包含带有主题和持久订阅者的 activemq。
（嵌入式）代理断开连接后，它不会获取在断开连接期间发送的消息，但会发送其本地待处理消息。
例子： 经纪商 A（嵌入式）<--->中央经纪商（独立）<---> Broker B（嵌入式）
Broker A 断开连接超过 30 秒（openwire 的最大不活动超时）后，它不会从中央 Broker 获取断开连接时发送的消息。但是，代理 A 发送了所有待处理消息，因此代理 B 接收了所有这些消息。
中央代理没有定义特定的网络连接器，因为事先不知道哪个代理必须连接到。
尝试了多种恢复策略，但似乎都不起作用。
有什么帮助吗？
We have a hub-and-spoke network topology with activemq with topic and durable subscribers.
After a (embedded) broker has been disconnected, it does not get the messages that have been sent during the disconnection period while it does send its local pending messages.
Example:
broker A (embedded) <---> central broker (standalone) <---> broker B (embedded)
After broker A has been disconnect for more than 30s (max innactivity timeout for openwire), it does not get from the central broker the messages that have been sent while disconnect. However, broker A sends all its pending messages so broker B receives all of them.
Central broker does not have a specific network connector defined, since it is not known before hand which brokers has to connect to.
Tried with several recovery policies, but none seems to work.
Any help?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
持久主题和集群代理存在各种问题...
如果可能，请尝试使用 虚拟主题 相反。它们设置简单，行为类似于持久队列，并且似乎更可靠......
there are various issues with durable topics and clustered brokers...
if possible, try using virtual topics instead. they are simple to setup, behave like persistent queues and seem to be much more reliable...