JBoss Messaging is a high performance JMS provider in the JBoss Enterprise Middleware Stack (JEMS). It is a complete rewrite of JBossMQ, which is the current default JMS provider in JBoss AS 4.0.x series and JBoss AS 4.2.0. JBoss Messaging will be the default JMS provider in JBoss AS 4.2.x series, probably starting with 4.2.1, and it is already the default provider in JBoss 5.0.0.Beta.

JBoss Messaging it is also the backbone of the JBoss ESB infrastructure.

Compared with JBossMQ, JBoss Messaging offers vastly improved performance in both single node and clustered environments. Please see this wiki page for performance benchmarks and Chapter 10, Generating Performance Benchmark Results on how to generate your own performance benchmarks. JBoss Messaging also features a much better modular architecture that will allow us to add more features in the future.

While JBoss Messaging only becomes the default JMS provider from JBoss AS 4.2.1 and JBoss 5.0, production users on JBoss AS 4.0.x can still take advantage of the performance improvements by easily replacing the JBossMQ module with JBoss Messaging.

The procedure of swapping JMS providers is presented in detail in this manual. In Chapter 5, JBoss Messaging Non-Clustered Installation we discuss how to install and use JBoss Messaging in JBoss 4.0.x production servers. We cover JBoss Messaging-specific configuration options, as well as how to run the build-in sanity / performance tests.

This guide is work in progress, as new features will be added to the 1.2 baseline at a very quick pace. Please send your suggestions or comments to the JBoss Messaging user forum.

Team:

Ovidiu Feodorov, Project Lead

Tim Fox, Technical Lead

Clebert Suconic, Core Messaging Developer

Other contributions by: Adrian Brock, Bela Ban, Alex Fu, Luc Texier, Aaron Walker, Rajdeep Dua, Madhusudhan Konda, Juha Lindfors and Ron Sigal.

This manual was written with help from Luc Texier, Lead Support EMEA and Sam Griffith Jr., JBoss Documentation Team.