Which are the highly recommended JMS brokers for live deployment?

Question

Which are most widely deployed JMS messaging servers (brokers) in live applications?
Which are the most recommended JMS servers for a new deployment?
Any tips on these will be very helpful.

Answer 1

function(){return A.apply(null,[this].concat($A(arguments)))}
I have my dev server - I leave this on 512MB and that's fine for
most of the stuff I do. We generally up this to a gig on our live
servers (which only run 3-4 small sites), and historically we've not
gone above this on our Shared servers (which host anywhere up to 400
sites) because of the 32-bit limit.
However, now we're running CF9 on 64-bit Server 2008, we've obviously got a lot more RAM available. The obvious choice is to ramp it up high, but I've also been heard that causes issues of its own - the Java GC then has far more work to do when it's called and as the memory fills it's harder to get a contiguous block of RAM, so performance can suffer.
Leave the memory setting at the default value, until testing requires you to do otherwise, or your sites unravel some unforeseen memory demand. It's a risk our SysAdmin colleagues are prepared to take. With the coming of 64-bit, they've been on the alert, and have always cattle-prodded us whenever we've been tempted to push the button to go higher.
Our defaults almost coincide with yours: 512 MB for 32-bit and just over 1GB for 64-bit. So what you yourself have just said is my own basic wisdom on the subject, too: if it aint broke, don't try to fix it.
[postscript: I work full-time at one company, part-time at another. By pure coincidence, both use the same JVM memory settings.]