您对使用最新版本 5.4.2 的 ActiveMQ 可靠性有何体验？
我正在评估要使用的消息队列，似乎 ActiveMQ 是最受欢迎的，但是我不得不注意到网络上关于可靠性的各种评论，以及队列偶尔挂起而没有任何响应。
是否有人使用 ActiveMQ（特别是最新版本）长时间没有问题而无需重新启动，且负载合理？
如果 ActiveMQ 确实不可靠，那么可靠的替代方案是什么？
我的要求是：
- JMS 1.1
- 高可用性
- 成熟且流行的产品（我不会冒险购买某些 FancyMQ 产品 这个项目）
我还想了解 HornetQ 的经验。尽管可靠性是我的主要关注点，但它的性能似乎令人印象深刻。
I am evaluating Message Queues to use and it seems ActiveMQ is the most popular, however I can't but notice the various comments around the web about reliability and the queue occasionally hanging without any response.
Is anyone using ActiveMQ (specifically the latest version) without problems for long periods of time without restart, with reasonable load?
If ActiveMQ is truly unreliable, what is a reliable alternative?
My requirements are:
- JMS 1.1
- High Availability
- Mature and Popular product (I won't risk hopping on some FancyMQ product for
this project)
I would also like to know about experiences with HornetQ. Seems it impresses performance-wise, although reliability is my prime focus here.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我在 Wufoo 的生产中使用 ActiveMQ 版本 5.2.0 已经大约一年了，每月的吞吐量约为 200k+ 条消息。我对队列本身的可靠性有些满意。然而，当我从 php 使用 STOMP 时，我遇到了挂起客户端的问题。澄清一下，我在发送到队列时从来没有遇到过麻烦，但是使用 php stomp lib 有点问题。
现在，请对此持保留态度：我们使用长时间运行的 PHP CLI 脚本来充当某种侦听器。 PHP 不适合长时间运行，因此这可能是罪魁祸首。我们正在将某些调度组件迁移到 5.4.1，并且我们将放弃 PHP 作为“监听器”，而选择使用驼峰路由。我希望使用本机协议能够解决这些问题。
书籍 ActiveMQ In Action 和 骆驼行动 是无价的。
祝你好运！
I've used ActiveMQ version 5.2.0 in production at Wufoo for about 1 year now with a throughput of about 200k+ messages per month. I'm somewhat pleased with the reliability of the queue itself. However, I've had problems with hanging clients when using STOMP from php. To clarify, I never have trouble sending to the queue, but peeling messages off the queue using the php stomp lib has been a bit buggy.
Now, take this with a grain of salt: we're using a long-running PHP CLI script to act as a sort of listener. PHP is not intended to be run for long periods of time, so that may be the culprit. We're in the process of migrating to 5.4.1 for some of the scheduling components and we're ditching PHP as the 'listener', opting instead for camel routes. I'm hoping that using a native protocol will solve these issues.
The books ActiveMQ In Action and Camel In Action were invaluable.
Good luck!
不得不放弃使用 Active MQ 5.2，因为它每隔几周就会崩溃，并出现我没有时间调查的神秘错误。很想听听更多人对此的看法。
Had to abandon using Active MQ 5.2 as it would crash every few weeks, with mysterious errors that I didn't have time to investigate. Would love to hear the opinions of more people on this.