[jboss-cvs] JBoss Messaging SVN: r2664 - in branches/Branch_1_0_1_SP: docs and 1 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed May 9 15:10:55 EDT 2007
Author: timfox
Date: 2007-05-09 15:10:53 -0400 (Wed, 09 May 2007)
New Revision: 2664
Modified:
branches/Branch_1_0_1_SP/build-thirdparty.xml
branches/Branch_1_0_1_SP/docs/README.html
branches/Branch_1_0_1_SP/tests/smoke/build.xml
Log:
Final commit for 1.0.1.sp5
Modified: branches/Branch_1_0_1_SP/build-thirdparty.xml
===================================================================
--- branches/Branch_1_0_1_SP/build-thirdparty.xml 2007-05-09 13:37:08 UTC (rev 2663)
+++ branches/Branch_1_0_1_SP/build-thirdparty.xml 2007-05-09 19:10:53 UTC (rev 2664)
@@ -92,7 +92,7 @@
<componentref name="jboss/common-logging-spi" version="2.0.2.GA"/>
<componentref name="jboss/aop" version="1.5.0.GA"/>
<componentref name="jboss/serialization" version="1.0.3.GA"/>
- <componentref name="jboss/remoting" version="2.2.0.SP3"/>
+ <componentref name="jboss/remoting" version="2.2.0.SP4"/>
<!-- Need this otherwise project doesn't build in Eclipse -->
<componentref name="apache-logging" version="1.0.4.1jboss"/>
Modified: branches/Branch_1_0_1_SP/docs/README.html
===================================================================
--- branches/Branch_1_0_1_SP/docs/README.html 2007-05-09 13:37:08 UTC (rev 2663)
+++ branches/Branch_1_0_1_SP/docs/README.html 2007-05-09 19:10:53 UTC (rev 2664)
@@ -26,84 +26,28 @@
<br>
<br>
<h2>Summary of Changes</h2>
-This service pack fixes several major bugs present in 1.0.1.SP2 and
+This service pack fixes several major bugs present in 1.0.1.SP4 and
previous releases.<br>
<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>
-Other bugs fixes address the following 1.0.1.SP2 problems:<br>
+
+Release Notes - JBoss Messaging - Version 1.0.1.SP5
+
+<h2>Bug</h2>
<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>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-622'>JBMESSAGING-622</a>] - JBossMessage.setJMSReplyTo() method does not allow to set up nulls</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-817'>JBMESSAGING-817</a>] - Db2 Persistence in Jboss</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-828'>JBMESSAGING-828</a>] - Use of pre configured ClientID on the database will change the pre configured clientID on the datasource</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-836'>JBMESSAGING-836</a>] - Deadlock on ServerConnectionEndpoint </li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-851'>JBMESSAGING-851</a>] - Issue with remoting MAX_RETRIES</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-852'>JBMESSAGING-852</a>] - Unacked message state is not cleaned up after failure in ack</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-864'>JBMESSAGING-864</a>] - Memory leak when using JCA layer and creating consumer on each send</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-885'>JBMESSAGING-885</a>] - Connecting to two JBoss messaging servers causes interference</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-886'>JBMESSAGING-886</a>] - Client unable to reconnect to JBoss 1.0.1.SP4 after restart</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-929'>JBMESSAGING-929</a>] - Implement a proper fix for JBMESSAGING-928</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-944'>JBMESSAGING-944</a>] - Messages ending up on different connections when there is more than one server</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-950'>JBMESSAGING-950</a>] - Unacked messages on recovery with JCA adaptor</li>
+<li>[<a href='http://jira.jboss.com/jira/browse/JBMESSAGING-954'>JBMESSAGING-954</a>] - We should be able to have multiple connections with the same client id....</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-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;">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>
</html>
Modified: branches/Branch_1_0_1_SP/tests/smoke/build.xml
===================================================================
--- branches/Branch_1_0_1_SP/tests/smoke/build.xml 2007-05-09 13:37:08 UTC (rev 2663)
+++ branches/Branch_1_0_1_SP/tests/smoke/build.xml 2007-05-09 19:10:53 UTC (rev 2664)
@@ -77,7 +77,7 @@
-->
<antcall target="installation-test">
- <param name="jboss.home" value="${jboss401sp1.home}"/>
+ <param name="jboss.home" value="${jboss401SP1.home}"/>
<param name="run.secure-socket.example" value="false"/>
</antcall>
@@ -99,11 +99,12 @@
<param name="run.secure-socket.example" value="false"/>
</antcall>
+<!--
<antcall target="installation-test">
<param name="jboss.home" value="${jboss403-installer.home}"/>
<param name="run.secure-socket.example" value="false"/>
</antcall>
-
+-->
<!--
4.0.3SP1
-->
More information about the jboss-cvs-commits
mailing list