JBoss Messaging 1.2.0.Beta2 has been released and it is available for download on jboss.org (http://labs.jboss.com/portal/jbossmessaging/downloads) and sourceforge (http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=157261).
1.2.0.Beta2 is functionally complete, with the exception of the "unreliable link scenario" (http://jira.jboss.org/jira/browse/JBMESSAGING-676),
whose development is still on-going on a parallel branch.
Beta2 includes full clustering, with load balancing and transparent failover. However, it is still a preview release, not all functional, stress and smoke tests pass, so do not attempt to use it in production. Also, the integration with the AS (installation, etc.) is at the moment a bit rough.
The messaging team is currently concentrating on releasing an almost-production-ready 1.2.0.CR1 shortly (a week from now). For CR1, the plan is to have all tests passing, and integrate seamlessly with the AS, but we will be waiting for the community feedback for a while after release
before going GA.
The final 1.2.0.GA is expected to be out at the end of February 2007.
The Beta2 release ships with clustering examples (which also double as smoke tests) that demonstrate distributed destinations and transparent failover capabilities. For the transparent failover example, a vanilla JMS client creates a connection to the JMS provider and sends message
over that connection. Separately, we kill the cluster node managing the connection (using System.halt(), to simulate an abrupt VM failure), but the event goes unnoticed by the client, which continues to send and receive messages over the same connection. Obviously, the example requires a cluster of at least two nodes in order to work.
The Messaging road map is available here: http://jira.jboss.org/jira/browse/JBMESSAGING?report=com.atlassian.jira.plugin.system.project:roadmap-panel.
