ActiveMQ 咨询主题的连接未在代理网络中转发?

发布于 2024-09-07 18:39:00 字数 476 浏览 5 评论 0原文

我正在开发一个应用程序,我们希望在其中监视客户端的登录/注销。由于 ActiveMQ 包含警告您新连接和删除连接的咨询主题,因此我们的想法是使用此咨询消息 (ActiveMQ.Advisory.Connection)。这在开发过程中工作得很好,但现在,当我们要在代理网络中进行生产时,我们注意到来自网络中远程代理的消息没有到达我们的消费者。

我们的设置是:

制作人 | 站点 1 中的代理 A 和 B(主从)->它们有一个双工网络连接器连接到站点 2 中的公共代理(C 和 D)

代理 C 和 D(又是主从)

并连接到 C 和 D,我们有我们想知道其登录/注销的“消费者”信息。

当我们在代理 A 的管理控制台中查看咨询主题时,我们会看到订阅者,并且如果我们让消费者连接,我们会收到登录消息。在 Broker C 上,我没有看到咨询主题的任何订阅者,并且当消费者登录/关闭时,我们看不到咨询消息。

这是默认行为还是我缺少配置?

I'm working on an application where we want to monitor logon/logoff of clients. Since ActiveMQ contains Advisory Topics that alert you of new connections and removal of connections, the idea was to use this advisory messages ( ActiveMQ.Advisory.Connection). This worked fine during development but now, when we are going to production in our network of brokers, we noticed that the messages from remote brokers in the network are not getting to our consumer.

Our setup is:

Producer
|
Broker A and B ( master Slave) in site 1 -> These have a duplex network connector to our public brokers (C & D)

Broker C and D (master slave again) in site 2

and attached to C and D, we have the "consumers" of whom we want to know logon/logoff information.

When we take a look at the advisory topic in the admin console on Broker A, we see the subscriber and we get logon messages if we let a consumer connect. On Broker C, I don't see any subscribers on the advisory topic, and when a consumers logs on / OFF, we don't see the advisory message.

Is this behaviour by default or am i missing a config?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

汐鸠 2024-09-14 18:39:00

您需要查找不同的地方:

  • 检查您的代理配置是否未禁用它们:在您的代理配置(A、B、C、D)中,检查咨询是否未禁用(我们不应该得到任何 。通常情况下,这似乎已经被检查过。
  • 检查您的代码是否未禁用它broker.setAdvisorySupport(false);。是根本原因,因为它在开发环境中工作
  • 您的目的地是动态的吗?检查的以下页面经纪商网络,特别是“动态网络”部分

There are different places you need to look for:

  • Check that your broker configuration does not disable them: in your broker configuration (A,B,C,D), check that the advisory are not disable (we shouldn't get any <broker advisorySupport="false">. Normally this seems to be checked already
  • Check that your code does not disable it broker.setAdvisorySupport(false);. This should not seem to be the root cause since it works in development environment
  • Are your destinations dynamic? Check the following page of Network of brokers, especially the section "Dynamic networks"
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文