What JMS implementation are you using?

Question

We use ActiveMQ 5.2 as our implementation of the choice, and we chose it some time ago. It works well enough for our use right now. Since it was a while, I was wondering what other implementations of the Java Message Service are used and why? Of course, there are more of them.

Answer 1

Before delving into JMS, consider also AMQP - there may be a new standard. JMS providers I worked with (to one degree or another):

TIBCO EMS is very fast and reliable, good API support, Java compatible, native C API. Best commercial choice I used.

Websphere MQ (and its implementation of JMS) - so, so. Pub / sub is not quite fast, many of the options and configuration options are "strange" and overly complex from the long history of this product. Just look at the amount of documentation ...

Solace JMS - very high bandwidth (a JMS broker is built into the hardware!), A good selection of connection protocols (MQTT, AMQP, XML via http as administrator protocols)

Fiorano MQ - was aggressive in marketing, but lost a lot of market share, maturity

Sonic MQ is a solid product that also supports API C

Active MQ - if you want to use an open source product (low-cost support, great community, limited add-ons, limited enterprise features), this is probably your best bet. Works out of the box and is the basis of several tools, such as Apache Camel, for example.

Answer 2

We rely on AMQ (5.1) through the Camel framework, and there were no problems. AMQ 4 was a bit more fishy.

Answer 3

WebLogic JMS provider when using WebLogic. It works great.

Answer 4

TIBCO EMS . This is a commercial messaging service with Java / JMS, C, .net and other bindings for it.

Answer 5

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

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

I heard that OpenMQ is more stable.

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

Answer 6

In one of the recent projects that I was in, we used Sonic MQ . Good general implementation with good .NET bindings.

We had a little scalability problem, but I have to admit that the scalability requirements were very strict: if I can correctly remember, something like 20,000 clutter per second without any delays between 200 different clients (each client had to receive every message at the same time).

Answer 7

I used JBossMQ, which ships with the JBoss application server up to version 4, and which is reliable but limited. JBoss Messaging was a replacement, comes with JBossAS 5, and this is a huge improvement.

ActiveMQ I have a real dislike. The developer (s) seems to have gone for performance and features to the detriment of stability, and this is phenomenally buggy. Given that this is a JMS fabric for Geronimo, I'm worried.

Answer 8

IBM WebSphere MQ 5 and 6 Active MQ 5.2.0

Also check out Micro QueueManager at http://codingjunky.com/page5/page4/page4.html It's small, easy to install and use for small projects.

Answer 9

We use SonicMQ, JBossMQ and the "micro broker" Lotus Expeditor Integrator. We use them for different purposes:

-JBossMQ is used internally and to communicate with all of our Java EE applications that run on JBoss. -Lotus Expeditor is used in "remote locations" where we have only limited resources and IT staff. -SonicMQ is our messaging system, we use it to connect central systems, as well as to connect remote systems in approx. 1000 sites.

We have good experience with all of them, but our experience also lies in the fact that in a more complex environment, you need to more actively administer the messaging system. This is especially true for SonicMQ on our website :-). In terms of performance, we did a great job with SonicMQ, especially in continuous queue-based messaging.

Answer 10

I used ActiveMQ for several years, but I was never happy with its stability (especially with clustering support). I never looked back after switching to OpenMQ. You might want to learn RabbitMQ or ZeroMQ.