JBoss Messaging 1.0.1.SP4 Release Notes

February 11, 2007

Installation

JBoss Messaging is a new JBoss JMS 1.1-compliant JMS provider, aimed to replace JBossMQ. An overview of its features, installation and configuration instructions are available in the "JBoss Messaging Getting Started Guide". The guide is bundled with this release and is provided in HTML, HTML-single and PDF formats. The guide is also available on-line at http://labs.jboss.com/portal/jbossmessaging/docs/index.html

Summary of Changes

This service pack fixes several major bugs present in 1.0.1.SP4 and previous releases.

Release Notes - JBoss Messaging - Version 1.0.1.SP5

Bug

[JBMESSAGING-622] - JBossMessage.setJMSReplyTo() method does not allow to set up nulls
[JBMESSAGING-817] - Db2 Persistence in Jboss
[JBMESSAGING-828] - Use of pre configured ClientID on the database will change the pre configured clientID on the datasource
[JBMESSAGING-836] - Deadlock on ServerConnectionEndpoint
[JBMESSAGING-851] - Issue with remoting MAX_RETRIES
[JBMESSAGING-852] - Unacked message state is not cleaned up after failure in ack
[JBMESSAGING-864] - Memory leak when using JCA layer and creating consumer on each send
[JBMESSAGING-885] - Connecting to two JBoss messaging servers causes interference
[JBMESSAGING-886] - Client unable to reconnect to JBoss 1.0.1.SP4 after restart
[JBMESSAGING-929] - Implement a proper fix for JBMESSAGING-928
[JBMESSAGING-944] - Messages ending up on different connections when there is more than one server
[JBMESSAGING-950] - Unacked messages on recovery with JCA adaptor
[JBMESSAGING-954] - We should be able to have multiple connections with the same client id....