Which JMS implementation do you use? [closed]

Solution 1:

Before delving into JMS, consider AMQP as well - might be a new standard. JMS providers I worked with (in varying degrees):

TIBCO EMS - very quick and robust, good API support, Java friendly, native C API exists. Best commercial choice I've used.

Websphere MQ (and its JMS implementation) - so, so. Pub/sub not exactly quick, many configurations options and choices are 'strange' and overly complex from the long history of that product. Just look at the amount of documentation...

Solace JMS - very high throughput (the JMS broker is built in hardware !), good choices of connecting protocols (MQTT, AMQP, XML over http as admin protocols)

Fiorano MQ - used to be agressive in marketing but lost a lot of market share, maturity concerns

Sonic MQ - solid product, also supports a C API

Active MQ - if you want to go with an open-source product (unexpensive support, great community, limited add-on products, limited enterprise features) this is probably your best choice. Works out of the box and is the backbone of several tools like Apache Camel, for example.

Solution 2:

We rely on AMQ (5.1) via the Camel framework, and there haven't been any issues. AMQ 4 was a tad more fishy.

Solution 3:

WebLogic JMS provider when using WebLogic. Works great.

Solution 4:

TIBCO EMS. It's a commercial message service with Java/JMS, C, .net, and other bindings for it.

Solution 5:

Sun's Open source OpenMQ (https://mq.dev.java.net/). You can get free and paid support for the same.

See this blog post about some comparison with ActiveMQ, etc -- http://alexismp.wordpress.com/2008/06/06/openmq-the-untold-story/.

I've heard that OpenMQ is more stable.

ActiveMQ is more flexible. as in, you can use it with more languages. There are probably more people on ActiveMQ's mailing list than OpenMQ.