I am pleased to announce the release of JBoss Messaging 1.4.0 Service Pack 1 (SP1).
This release contains several bug fixes; a few relating to some failover edge cases, an important fix in byte message handling, some sanity checking and configuration changes in JBoss Remoting and several smaller issues. For full description of the contents please see the JBoss Messaging project JIRA.
You can download it here http://labs.jboss.com/jbossmessaging/downloads/
In this release we have also switched to using the TCP MPING JGroups stack by default for data traffic. This has shown to perform better for small cluster sizes. For large clusters its likely you'll want to use a UDP based stack.
When upgrading an existing installation be sure to update all the configuration files in server/<server name>/deploy/jboss-messaging.sar with the newer versions and replace jboss-messaging.jar in server/<server name>/lib and on the client classpath. You will also need to drop all tables and indexes in the database.
This release of JBoss Messaging, like 1.4.0.GA also requires a patched JBoss Remoting jar. The required version is 2.2.2.SP1, the same as that required by JBoss Messaging 1.4.0.GA. Be sure that server/<server name>/lib contains this jar and that it is also present as the first entry on the client classpath.
JBoss Messaging 1.4.0 requires Java 5 or later to run.