Enterprise Messaging News (June 2011)

HornetQ 2.2.5 Message Broker released

June 17, 2011 – HornetQ 2.2.5.Final, available for download now, will be the first release included as the default Java Message System (JMS) provider in the JBoss AS 7 Java EE application server. Changes and bug fixes also include an issue in the Stomp Decoder. HornetQ is an open source project from the JBoss Community to build a multi-protocol, embeddable, very high performance, clustered, asynchronous messaging system. It supports non-Java clients and is already the default JMS provider in JBoss AS 6.

RabbitMQ 2.5.0 AMQP Message Broker released

June 14, 2011 – RabbitMQ 2.5.0 new features include a tracing facility for debugging incoming and outgoing messages, improved inbound network and routing performance, and SSL support for the STOMP adapter. RabbitMQ is an independent open-source implementation of AMQP. Over its STOMP transport adapter plugin, clients can be implemented in many languages, including Delphi and Free Pascal.

OpenMQ 4.6 New Features for Cloud-Enabled Messaging

OpenMQ 4.6 will be a minor feature update to support the GlassFish 3.2 project. Key feature goals of that project include enabling deployment in various cloud based services. OpenMQ is the Java Message Service (JMS) reference implementation, can run in embedded or standalone mode, and supports non-Java clients.

“JBoss Application Server 7 – What’s coming?” by Jason Shepherd

In this article, Jason Shepherd writes that “JBoss Application Server (AS) 7 is due for release in early June”. The Modular Service Container (MSC) in JBoss AS 7 is a complete rewrite. Features and improvements include much faster startup, class loading improvements, a single file for configuration, a new command line configuration and management interface, and more. For enterprise messaging, JBoss AS 7 includes HornetQ as the embedded JMS provider and for message driven beans.

“When to use Apache Camel?” – by Kai Wähner

In this blog post, Kai Wähner writes about Apache Camel, a open source integration framework based on Enterprise Integration Patterns with powerful Bean Integration: “Almost every technology you can imagine is available, for example HTTP, FTP, JMS, EJB, JPA, RMI, JMX, LDAP, Netty, and many, many more“. His conclusion is that “Apache Camel is an awesome framework to integrate applications with different technologies. The best thing is that you always use the same concepts.“. Apache Camel is also integrated in Apache ActiveMQ (an open source message broker) and in Apache ServiceMix (Enterprise Service Bus).

“Multithreading – Fear, Uncertainty and Doubt” by Steve Lott

In his article, Steve Lott suggests message queues as the best kind of lock for concurrency in multi-threaded applications: “The various concurrent elements can simply dequeue pieces of data, do their tasks and enqueue the results. It’s really elegant. It has many, simple, uncoupled pieces. It can be scaled by increasing the number of threads sharing a queue.” – As an example, he shows that the Dining Philosophers Code Kata has a queue-based solution that’s pretty cool. He also notices “Too many questions on StackOverflow seem to have simple message queue solutions. But folks seem to start out using inappropriate technology.“