Release Notes - JBoss Messaging - Version 1.4.0.SP3_CP03
25 June 2008
These are the release notes for JBoss Messaging 1.4.0 Service Pack 3 (SP3) CP03
For full description of the contents please see the JBoss Messaging project JIRA.
This is a release according to the Cumulative Patch process defined by JBoss EAP
Important note on upgrading JBM versions
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 also requires a patched JBoss Remoting jar. The required version is 2.2.2.SP8-brew. This is available from the JBoss public jar repository. (repository.jboss.com) Be sure that server/<server name>/lib contains this jar and that it is also present as the first entry on the client classpath. This is critical to ensure proper operation of JBoss Messaging!
Enjoy!
Tasks completed on this release
Bug
- [JBMESSAGING-1277] - In some edge cases, Object Isolation is broken on ObjectMessage
- [JBMESSAGING-1286] - Broken command line on UNIX platforms other than Linux causes many testsuite tests to fail.
- [JBMESSAGING-1377] - Typo in default HSQL persistence config
- [JBMESSAGING-1386] - Two different topic subscribers in two different sessions get the same reference to an Object. The object should be serialized.
Task