{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 forever°为你锁心 的问题《Active MQ vs JBoss Messaging》','https://www.manongdao.com/q-468205.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
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.
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.
HornetQ looks good.
http://www.spec.org/jms2007/results/jms2007.html
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 very dated (not to mention probably biased).
JBoss Messaging replaces JBoss MQ. Here are Messaging performance data: http://www.jboss.org/community/docs/DOC-10640
JBoss MQ is not scalable at all: http://www.jboss.org/community/docs/DOC-12452
JBoss Messaging is now in bug fix mode only, since JBoss / Red Hat has a new Java messaging project called HornetQ.
The web site is here http://hornetq.org
HornetQ boasts extreme performance, a full feature set and ease of use.
You'll find it's performance compared to ActiveMQ is extremely good.
BTW - I am the project lead for JBoss Messaging and HornetQ.
HornetQ 2.0.0.GA is out in the next week.
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.
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.
Take a look at this. Apparently there are certain concern when it comes to persistent storage in ActiveMQ.
http://www.jboss.org/file-access/default/members/jbossmessaging/freezone/docs/userguide-2.0.0.alpha1/html/performance.html#performance.results
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.
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.