JBoss Messaging 1.3.0.GA Release Notes

1st June 2007

JBoss Messaging is the new JBoss JMS 1.1-compliant JMS provider. An extensive overview of its features, as well as installation and configuration instructions are available in the "JBoss Messaging 1.3 User 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
Release Notes - JBoss Messaging - Version 1.3.0.GA

Bug

[JBMESSAGING-511] - JDBC and Transaction close/cleanup operations should be bullet-proofed in JDBCChannelMapper and elsewhere.
[JBMESSAGING-622] - JBossMessage.setJMSReplyTo() method does not allow to set up nulls
[JBMESSAGING-915] - Sybase Persistence Problem - CLUSTERED is a keyword
[JBMESSAGING-916] - CLONE -JDBCPersistenceManager and JDBCSupport do not close Statements
[JBMESSAGING-926] - Negative message count
[JBMESSAGING-929] - Implement a proper fix for JBMESSAGING-928
[JBMESSAGING-930] - Error closing a session
[JBMESSAGING-935] - Extraneous file in jboss-messaging-1.2.0.sp1-src
[JBMESSAGING-939] - ClientID null if using preConfigured ConnectionFactories
[JBMESSAGING-943] - Investigate problem with failover
[JBMESSAGING-946] - JmsXA should behave the same way as JBossMQ
[JBMESSAGING-950] - Unacked messages on recovery with JCA adaptor
[JBMESSAGING-951] - Infinite Loop over Expiration to a queue
[JBMESSAGING-953] - Can delete temp queue when it has active consumers
[JBMESSAGING-954] - We should be able to have multiple connections with the same client id....
[JBMESSAGING-955] - Potential issue in calling JBM from web application
[JBMESSAGING-959] - Potential issue in MDB reconnection
[JBMESSAGING-960] - ClusteredPostOffices are bound to 127.0.0.1 on JGroups config
[JBMESSAGING-962] - Fix deadlock in PointToMultipointRouter
[JBMESSAGING-971] - Race condition in message redistribution
[JBMESSAGING-975] - Getting message payload returns null after messages is serialized
[JBMESSAGING-978] - NullPointerException within DefaultClusteredPostOffice.handleMessagePullResult()

Feature Request

[JBMESSAGING-804] - Provide a clean jboss-messaging-client.jar without containing external dependencies
[JBMESSAGING-843] - Clustered ConnectionFactory with no load balancing, but failover capabilities needed
[JBMESSAGING-948] - ClusteredPostOffice should throw an exception when two nodes are started with the same ID
[JBMESSAGING-952] - Drop the requirement of multiple clientIDs
[JBMESSAGING-957] - Provide a configuration(installation) that will work in the All configuration.
[JBMESSAGING-961] - WebServices SmokeTest
[JBMESSAGING-976] - Security config is not set

Task

[JBMESSAGING-925] - Remove requirement to deploy JBM scoped in JB AS <= 4.2
[JBMESSAGING-932] - Add tests to verify duplicatedClients according to TCK
[JBMESSAGING-933] - Complete and tidy documentation
[JBMESSAGING-940] - Provide slimmed down client jar
[JBMESSAGING-956] - Implement clustered temporary queues
[JBMESSAGING-966] - Create clustered ejb smoke test
[JBMESSAGING-968] - Update documentation on installation procedures
[JBMESSAGING-973] - Tune JBR service settings