java 主动 MQ 与 JBoss 消息传递
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/507391/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Active MQ vs JBoss Messaging
提问by maskefjes
I am going to choose a JMS message broker for a project. It is critical that the JMS server is stable and can handle a high load of messages. I have narrowed down the list to include Active MQ and JBoss Messaging.
我将为一个项目选择一个 JMS 消息代理。JMS 服务器稳定并且可以处理高负载的消息至关重要。我已经缩小了列表的范围以包括 Active MQ 和 JBoss Messaging。
I was wondering if any of you have any experience with any of these or even better have tried both of them in the same environment. Any link to a research paper or similar would be nice.
我想知道你们中是否有任何人对这些有任何经验，或者更好的是在同一环境中尝试过这两种方法。任何指向研究论文或类似文章的链接都会很好。
回答by Tim Fox
JBoss Messaging is now in bug fix mode only, since JBoss / Red Hat has a new Java messaging project called HornetQ.
JBoss Messaging 现在仅处于错误修复模式，因为 JBoss / Red Hat 有一个名为 HornetQ 的新 Java 消息传递项目。
The web site is here http://hornetq.org
网站在这里http://hornetq.org
HornetQ boasts extreme performance, a full feature set and ease of use.
HornetQ 拥有卓越的性能、完整的功能集和易用性。
You'll find it's performance compared to ActiveMQ is extremelygood.
您会发现它的性能与 ActiveMQ 相比非常好。
BTW - I am the project lead for JBoss Messaging and HornetQ.
顺便说一句 - 我是 JBoss Messaging 和 HornetQ 的项目负责人。
HornetQ 2.0.0.GA is out in the next week.
HornetQ 2.0.0.GA 将在下周发布。
回答by IAdapter
回答by James
JBoss recently redid their entire implementation of Messaging, ala JBoss MQ has been replaced with JBoss Messaging, and now again as "HornetQ". You'll just want to keep that in mind as that above comparison is verydated (not to mention probably biased).
JBoss 最近重做了他们整个 Messaging 的实现，ala JBoss MQ 已经被 JBoss Messaging 取代，现在又是“HornetQ”。你只是想记住这一点与上述比较是非常过时（更不用说可能优先）。
回答by skaffman
Feature-by-feature comparisons are all very well, but my experience of ActiveMQ (through various versions over the years) is that it is shockingly buggy, and noone seems inclined to fix those bugs. It's deeply frustrating. Also, the documentation is messy and not properly updated with new versions.
逐个特性的比较都非常好，但我对 ActiveMQ 的体验（多年来通过各种版本）是它的错误令人震惊，而且似乎没有人倾向于修复这些错误。这令人非常沮丧。此外，文档很乱，没有正确更新新版本。
JBossMessaging is relatively feature-light, compared to ActiveMQ, but it's rock-solid, well-documented and reliable. It's also part of JBossAS 5, and RedHat are doing a good job of supporting it.
与 ActiveMQ 相比，JBossMessaging 的功能相对较少，但它坚如磐石、文档齐全且可靠。它也是 JBossAS 5 的一部分，RedHat 在支持它方面做得很好。
回答by paradisontheitroad
So far, I had a great experience with the community wiki and documentation of Jboss, and it pretty much covers everything. Though, I found quite obvious configuration settings left out in their latest documentations, but I guess this must have been improved since then. For ActiveMQ, I found very little documentation comparing to Jboss.
到目前为止，我在社区 wiki 和 Jboss 文档方面拥有丰富的经验，它几乎涵盖了所有内容。虽然，我发现他们的最新文档中遗漏了非常明显的配置设置，但我想从那时起这肯定已经得到改进。对于 ActiveMQ，我发现与 Jboss 相比的文档很少。
I have done certain research using MOM with Jboss and GlassFish, but one of the most important impact was the permanent storage if you are going to use any. I think this itself is very important, especially their compatibility, support, documentations.
我使用 Jboss 和 GlassFish 使用 MOM 进行了某些研究，但最重要的影响之一是永久存储，如果您打算使用任何存储。我认为这本身非常重要，尤其是它们的兼容性、支持、文档。
Take a look at this. Apparently there are certain concern when it comes to persistent storage in ActiveMQ.
看看这个。显然，当谈到 ActiveMQ 中的持久性存储时，存在一定的担忧。
回答by SteJav
回答by avro
JBoss Messaging replaces JBoss MQ. Here are Messaging performance data: http://www.jboss.org/community/docs/DOC-10640
JBoss Messaging 取代了 JBoss MQ。以下是消息性能数据：http: //www.jboss.org/community/docs/DOC-10640
JBoss MQ is not scalable at all: http://www.jboss.org/community/docs/DOC-12452
JBoss MQ 根本无法扩展：http: //www.jboss.org/community/docs/DOC-12452
