简体   繁体   English

任何通过ActiveMQ使用多播的人

[英]Anyone using multicast with ActiveMQ

I'm having trouble setting up multicast transport using ActiveMQ. 我在使用ActiveMQ设置多播传输时遇到问题。 I noticed with version 5.2 there is a bug that prevents it from even building the correct factory (fixed in 5.3). 我注意到5.2版存在一个错误,该错误使它甚至无法构建正确的工厂(已在5.3中修复)。 The fact this bug exists makes me wonder if anyone is using multicast at all . 这个bug存在,这一事实使我如果有人使用多播的所有怀疑。 How can this be tested when it only recently has been enabled? 仅在最近启用时如何测试?

Just knowing that this is possible would help me a lot. 知道这是可能的,对我有很大帮助。 Thanks. 谢谢。

EDIT: 编辑:

It turns out i was hanging on building the connection. 事实证明,我一直在建立连接。 The setClientID is a synchronous call, so the client sits and waits indefinitely. setClientID是一个同步调用,因此客户端可以坐下来无限期地等待。 This is a landmine for anyone using multicast, there are many calls in the AMQConnection object that call ensureConnectionInfoSent() that blocks until it receives a response. 对于使用多播的任何人来说,这都是一个地雷。AMQConnection对象中有许多调用,它们会确保直到收到响应之前一直阻塞,这些调用会确保sureConnectionInfoSent() This is just incompatible with multicast. 这只是与多播不兼容。

I have seen the multicast transport work in the past, in a development rather than production context. 过去,我已经看到了多播传输在开发而不是生产环境中的工作。 It seemed a bit flaky, though, and didn't give me the confidence to trust it where there's money on the line. 但是,这似乎有些不稳定,也没有给我信心去相信有钱的地方。

IMO, ActiveMQ is ridiculously buggy. IMO,ActiveMQ令人毛骨悚然。 The most basic bugs seem to creep into the codebase on a regular basis, and it's very hard to have confidence that they can do the difficult things when the basics go wrong so often. 最基本的错误似乎会定期出现在代码库中,并且很难确定当这些基本错误经常发生时,它们会做困难的事情。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM