[jboss-cvs] JBoss Messaging SVN: r3404 - in branches/Branch_Stable/docs: userguide/en/modules and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Dec 3 12:36:12 EST 2007
Author: timfox
Date: 2007-12-03 12:36:11 -0500 (Mon, 03 Dec 2007)
New Revision: 3404
Modified:
branches/Branch_Stable/docs/README.html
branches/Branch_Stable/docs/userguide/en/modules/installation.xml
Log:
Updated README
Modified: branches/Branch_Stable/docs/README.html
===================================================================
--- branches/Branch_Stable/docs/README.html 2007-12-03 16:30:24 UTC (rev 3403)
+++ branches/Branch_Stable/docs/README.html 2007-12-03 17:36:11 UTC (rev 3404)
@@ -3,64 +3,55 @@
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="content-type">
- <title>JBoss Messaging 1.4.0.SP1 Release Notes</title>
+ <title>JBoss Messaging 1.4.0.SP2 Release Notes</title>
</head>
<body>
-<h1>Release Notes - JBoss Messaging - Version 1.4.0.SP1</h1>
+<h1>Release Notes - JBoss Messaging - Version 1.4.0.SP2</h1>
<br>
-<h2>31 August 2007</h2>
+<h2>03 December 2007</h2>
-These are the release notes for JBoss Messaging 1.4.0 Service Pack 1 (SP1).<br><br>
+These are the release notes for JBoss Messaging 1.4.0 Service Pack 2 (SP2).<br><br>
For full description of the contents please see the JBoss Messaging project JIRA.<br><br>
-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.<br><br>
-
-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.<br><br>
-
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.<br><br>
-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.<br><br>
+This release of JBoss Messaging, like 1.4.0.GA also requires a patched JBoss Remoting jar. The required version is 2.2.2.GA_CP03. Be sure that server/<server name>/lib contains this jar and that it is also present as the first entry on the client classpath.<br><br>
Enjoy!<br><br>
-<br><br>
+Release Notes - JBoss Messaging - Version 1.4.0.SP2
<h2>Bug</h2>
<ul>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1079'>JBMESSAGING-1079</a>] - JBM should call BytesMessage.reset() before redelivery, or not redeliver the same message instance</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1091'>JBMESSAGING-1091</a>] - Selector parser should use string literals for DeliveryMode in selector expressions</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1095'>JBMESSAGING-1095</a>] - ServerPeer won't survive a stop/start of the service</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1098'>JBMESSAGING-1098</a>] - Message headers not preserved on bridged message</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1099'>JBMESSAGING-1099</a>] - Potential deadlock in shutting down server</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1100'>JBMESSAGING-1100</a>] - Non durable topic subscribers with noLocal=true result in message build up on server</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1101'>JBMESSAGING-1101</a>] - Failure to deserialize BytesMessage contents</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1109'>JBMESSAGING-1109</a>] - Client-side race condition while receiving concurrently</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1110'>JBMESSAGING-1110</a>] - Client incorrectly initiates client-side fail over on high concurrency</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1112'>JBMESSAGING-1112</a>] - Consumption with highly concurrent clients lock a JBM server node.</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1113'>JBMESSAGING-1113</a>] - Post office and message updates at failover need to be transactional</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1114'>JBMESSAGING-1114</a>] - JBoss Remoting fails under load</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1115'>JBMESSAGING-1115</a>] - java.net.SocketException: Too many open files</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1116'>JBMESSAGING-1116</a>] - Consuming client grinds to a halt if a node different from the "active" one fails</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1118'>JBMESSAGING-1118</a>] - Sucker connection created back to itself doesn't need to be created</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1120'>JBMESSAGING-1120</a>] - Data channel from MultiplexerChannelFactory prevents state transfers from other users of the shared channel</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1124'>JBMESSAGING-1124</a>] - Cannot find replicant to remove: CF_jboss.messaging.connectionfactory:service=ConnectionFactory</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1136'>JBMESSAGING-1136</a>] - Messages do not get redistributed to consumers following shutdown/restart sequence</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1138'>JBMESSAGING-1138</a>] - Setting Vector in an ObjectMessage returns a different Object</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1139'>JBMESSAGING-1139</a>] - Problem with DownCache storage at JBM startup</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1142'>JBMESSAGING-1142</a>] - If two servers are started at the same time a race condition can exist between calculating the failover nodes.</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1146'>JBMESSAGING-1146</a>] - Messaging fails to shutdown when there are no more ManagedConnections available</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1156'>JBMESSAGING-1156</a>] - Calling Browser.Enumeration on deleted temporary queue is not throwing InvalidDestinationException</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1158'>JBMESSAGING-1158</a>] - Sending messages on deleted temporary topicc should cause an Exception to be thrown</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1159'>JBMESSAGING-1159</a>] - Deadlocks with ClusterRoundRobinDistributor</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1164'>JBMESSAGING-1164</a>] - Killing a client with a registered MessageListener renders the queue (and ServerPeer) unusable</li>
</ul>
<h2>Feature Request</h2>
<ul>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1047'>JBMESSAGING-1047</a>] - ServerPeer.listMessageCountersAsHTML sorted by Name</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1119'>JBMESSAGING-1119</a>] - We should ignore nonPersistentMessages on failover</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1155'>JBMESSAGING-1155</a>] - Synchronize users on examples with user names and roles used on JBAS testsuite</li>
</ul>
<h2>Task</h2>
<ul>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-999'>JBMESSAGING-999</a>] - Bridge startup should retry if remote destinations are not available</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1096'>JBMESSAGING-1096</a>] - Remove references from the old Callback Manager on the documentation</li>
-<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1129'>JBMESSAGING-1129</a>] - Change default data stack to TCP</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1130'>JBMESSAGING-1130</a>] - Remove unused column INS_TIME</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1152'>JBMESSAGING-1152</a>] - Investigate whether we should include state column in tx index</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1153'>JBMESSAGING-1153</a>] - Optimisation for message sucking</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1165'>JBMESSAGING-1165</a>] - Fix remoting configuration under ServiceContainer</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-1166'>JBMESSAGING-1166</a>] - Add workaround for JBREM-845 </li>
</ul>
Modified: branches/Branch_Stable/docs/userguide/en/modules/installation.xml
===================================================================
--- branches/Branch_Stable/docs/userguide/en/modules/installation.xml 2007-12-03 16:30:24 UTC (rev 3403)
+++ branches/Branch_Stable/docs/userguide/en/modules/installation.xml 2007-12-03 17:36:11 UTC (rev 3404)
@@ -496,8 +496,8 @@
jboss-remoting.jar. This version is not available in the
JBoss AS 4.2.0 or JBoss AS 4.2.1 distributions. The patched
jar can be found <ulink
- url="http://repository.jboss.com/jboss/remoting/2.2.2.SP1-brew/lib/">here</ulink>The
- version is JBoss Remoting 2.2.2.SP1-brew. Please download it
+ url="http://repository.jboss.com/jboss/remoting/2.2.2.GA_CP03/lib/">here</ulink>The
+ version is JBoss Remoting 2.2.2.GA_CP03. Please download it
and copy it into the <literal>$JBOSS_HOME/server/<your
server name>/lib directory</literal> of any server
profiles that use JBoss Messaging 1.4.0. If you are using
More information about the jboss-cvs-commits
mailing list