[jboss-cvs] JBoss Messaging SVN: r2260 - branches/Branch_1_0_1_SP/docs.

Sun Feb 11 04:02:04 EST 2007

Author: ovidiu.feodorov at jboss.com
Date: 2007-02-11 04:02:04 -0500 (Sun, 11 Feb 2007)
New Revision: 2260

Modified:
   branches/Branch_1_0_1_SP/docs/README.html
Log:
release notes for 1.0.1.SP4

Modified: branches/Branch_1_0_1_SP/docs/README.html
===================================================================

--- branches/Branch_1_0_1_SP/docs/README.html	2007-02-11 09:01:35 UTC (rev 2259)
+++ branches/Branch_1_0_1_SP/docs/README.html	2007-02-11 09:02:04 UTC (rev 2260)
@@ -7,9 +7,9 @@
 </head>
 <body>
 <h1><br>
-JBoss Messaging 1.0.1.SP3 Release Notes</h1>
+JBoss Messaging 1.0.1.SP4 Release Notes</h1>
 <br>
-January 18, 2007<br>
+February 11, 2007<br>
 <br>
 <h2>Installation</h2>
 <br>
@@ -26,24 +26,83 @@
 <br>
 <br>
 <h2>Summary of Changes</h2>
+This service pack fixes several major bugs present in 1.0.1.SP2 and
+previous releases.<br>
 <br>
-This is a bug fix release. It fixes a major remoting bug (<a
- href="http://jira.jboss.org/jira/browse/JBMESSAGING-748">JBMESSAGING-748</a>)
-plus some other minor ones.<br>
+The most serious is <a
+ href="http://jira.jboss.org/jira/browse/JBMESSAGING-721">http://jira.jboss.org/jira/browse/JBMESSAGING-721</a>,
+which was causing message redelivery not to function properly. This bug
+fix alone should justify an upgrade to 1.0.1.SP4, especially if you use
+Message Driven Beans and Container Managed Transactions.<br>
 <br>
+Another potentially dangerous misbehavior is
+<a href="http://jira.jboss.org/jira/browse/JBMESSAGING-787">http://jira.jboss.org/jira/browse/JBMESSAGING-787</a>
+that was causing
+long-running invocations (such as sending a large transaction to the
+server) to time out inadvertently. The root cause was identified to be
+<a href="http://jira.jboss.org/jira/browse/JBREM-691">http://jira.jboss.org/jira/browse/JBREM-691</a>.
+The new
+Remoting library incorporated by 1.0.1.SP4 contains the fix for this
+bug.<br>
 <br>
-<h2>Release Notes </h2>
-<h2 style="margin-left: 40px;">Bug</h2>
+Other bugs fixes address the following 1.0.1.SP2 problems:<br>
+<ul>
+  <li>Broken QueueBrowser behavior (<a
+ href="http://jira.jboss.org/jira/browse/JBMESSAGING-803">http://jira.jboss.org/jira/browse/JBMESSAGING-803</a>)</li>
+  <li>Non-compliant client ID behavior - the previous version
+allowed simultaneous clients with same client ID
+(<a href="http://jira.jboss.org/jira/browse/JBMESSAGING-791">http://jira.jboss.org/jira/browse/JBMESSAGING-791</a>)</li>
+  <li>Incorrect handling of the replyTo property for persistent
+messages
+in some situations (<a
+ href="http://jira.jboss.org/jira/browse/JBMESSAGING-757">http://jira.jboss.org/jira/browse/JBMESSAGING-757</a>)</li>
+  <li>Corruption of the security context in managed environment (<a
+ href="http://jira.jboss.org/jira/browse/JBMESSAGING-807">http://jira.jboss.org/jira/browse/JBMESSAGING-807</a>)</li>
+  <li>Potential deadlock during the client initialization (<a
+ href="http://jira.jboss.org/jira/browse/JBMESSAGING-800">http://jira.jboss.org/jira/browse/JBMESSAGING-800</a>)</li>
+  <li>Memory leaks (<a
+ href="http://jira.jboss.org/jira/browse/JBMESSAGING-638">http://jira.jboss.org/jira/browse/JBMESSAGING-638</a>)</li>
+</ul>
+<br>
+<h2>Release Notes</h2>
+<h2 style="margin-left: 40px;">Bugs</h2>
 <ul style="margin-left: 40px;">
-  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-741">JBMESSAGING-741</a>]
-- Message.getJMSDestination could be null on redeployment of a queue</li>
-  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-748">JBMESSAGING-748</a>]
-- Messaging server can be locked up by broken or malicious clients</li>
-  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-749">JBMESSAGING-749</a>]
-- Connection Timeouts that can lead to Serialization Exceptions</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-417">JBMESSAGING-417</a>]
+- JMS Client does not exit</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-638">JBMESSAGING-638</a>]
+- Potential memory leak when using 2pc via JCA adapter.</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-664">JBMESSAGING-664</a>]
+- The 4.0.5.GA jnlp installer smoke test fails</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-721">JBMESSAGING-721</a>]
+- Message redelivery doesn't work </li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-757">JBMESSAGING-757</a>]
+- JDBCPersistenceManager incorrectly detects if a replytoId was null
+when restoring a message from a ResultSet</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-787">JBMESSAGING-787</a>]
+- Invocations time out because remoting mismanages client invokers,
+sending bussines traffic over client invokers with small timeout</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-791">JBMESSAGING-791</a>]
+- Duplicates clientIDs are not throwing InvalidClientIDException</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-800">JBMESSAGING-800</a>]
+- Deadlock in aop stack deployment</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-803">JBMESSAGING-803</a>]
+- QueueBrowser doesn't refresh the content of its Enumeration on the
+second getEnumeration() call</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-807">JBMESSAGING-807</a>]
+- security context switch after sending a message</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-821">JBMESSAGING-821</a>]
+- org.jboss.test.messaging.core.paging tests fail in-VM on Linux</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-824">JBMESSAGING-824</a>]
+- queue smoke test fails</li>
 </ul>
-<h2 style="margin-left: 40px;"><br>
-</h2>
+<h2 style="margin-left: 40px;">Tasks</h2>
+<ul style="margin-left: 40px;">
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-755">JBMESSAGING-755</a>]
+- Bring mdb-failure's README.html up to date</li>
+  <li>[<a href="http://jira.jboss.com/jira/browse/JBMESSAGING-756">JBMESSAGING-756</a>]
+- Enable mdb-failure smoke test so it will run with the smoke test suite<br>
+  </li>
+</ul>
 <br>
 <hr style="width: 100%; height: 2px;">
 </body>


