[jboss-cvs] JBoss Messaging SVN: r4006 - in branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs: userguide/en/modules and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Apr 4 05:40:17 EDT 2008
Author: timfox
Date: 2008-04-04 05:40:17 -0400 (Fri, 04 Apr 2008)
New Revision: 4006
Modified:
branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/README.html
branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/installation.xml
Log:
Updated docs and readme for remoting versions and upgrade instructions
Modified: branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/README.html
===================================================================
--- branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/README.html 2008-04-04 08:56:32 UTC (rev 4005)
+++ branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/README.html 2008-04-04 09:40:17 UTC (rev 4006)
@@ -11,15 +11,17 @@
<br>
-<h2>13 December 2007</h2>
+<h2>04 April 2008</h2>
These are the release notes for JBoss Messaging 1.4.0 Service Pack 3 (SP3) CP02<br><br>
For full description of the contents please see the JBoss Messaging project JIRA.<br><br>
+<h2>Important note on upgrading JBM versions</h2>
+
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 also requires a patched JBoss Remoting jar. The required version is 2.2.2.SP5. Be sure that server/<server name>/lib contains this jar and that it is also present as the first entry on the client classpath. This is critical to ensure proper operation of JBoss Messaging 1.4.0.SP3!<br><br>
+This release of JBoss Messaging also requires a patched JBoss Remoting jar. The required version is 2.2.2.SP7-brew. This is available from the JBoss public jar repository. (repository.jboss.com) Be sure that server/<server name>/lib contains this jar and that it is also present as the first entry on the client classpath. This is critical to ensure proper operation of JBoss Messaging!<br><br>
Enjoy!<br><br>
Modified: branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/installation.xml
===================================================================
--- branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/installation.xml 2008-04-04 08:56:32 UTC (rev 4005)
+++ branches/Branch_JBossMessaging_1_4_0_SP3_CP/docs/userguide/en/modules/installation.xml 2008-04-04 09:40:17 UTC (rev 4006)
@@ -165,7 +165,6 @@
<attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
<attribute name="dataType" isParam="true">jms</attribute>
<attribute name="socket.check_connection" isParam="true">false</attribute>
- <attribute name="timeout" isParam="true">0</attribute>
<attribute name="serverBindAddress">${jboss.bind.address}</attribute>
<attribute name="serverBindPort">4657</attribute>
<attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
@@ -178,6 +177,8 @@
<!-- Periodicity of client pings. Server window by default is twice this figure -->
<attribute name="clientLeasePeriod" isParam="true">10000</attribute>
+ <attribute name="timeout" isParam="true">0</attribute>
+
<!-- Number of seconds to wait for a connection in the client pool to become free -->
<attribute name="numberOfRetries" isParam="true">10</attribute>
@@ -407,8 +408,7 @@
<attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
<attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
<attribute name="dataType" isParam="true">jms</attribute>
- <attribute name="socket.check_connection" isParam="true">false</attribute>
- <attribute name="timeout" isParam="true">0</attribute>
+ <attribute name="socket.check_connection" isParam="true">false</attribute>
<attribute name="serverBindAddress">${jboss.bind.address}</attribute>
<attribute name="serverBindPort">4657</attribute>
<attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
@@ -424,6 +424,8 @@
<!-- Number of seconds to wait for a connection in the client pool to become free -->
<attribute name="numberOfRetries" isParam="true">10</attribute>
+ <attribute name="timeout" isParam="true">0</attribute>
+
<!-- Max Number of connections in client pool. This should be significantly higher than
the max number of sessions/consumers you expect -->
<attribute name="JBM_clientMaxPoolSize" isParam="true">200</attribute>
@@ -494,8 +496,8 @@
<para>
<note>JBoss Messaging 1.4.0 requires a patched version of
jboss-remoting.jar. This version is available on JBoss EAP 4.3, so if you're using a different version of JBoss you should download the patched version which can be found <ulink
- url="http://repository.jboss.com/jboss/remoting/2.2.2.SP4-brew/ ">here</ulink>The
- version is JBoss Remoting 2.2.2.SP4-brew. Please download it
+ url="http://repository.jboss.com/jboss/remoting/2.2.2.SP7-brew/ ">here</ulink>The
+ version is JBoss Remoting 2.2.2.SP7-brew. 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
@@ -764,9 +766,9 @@
<itemizedlist>
<listitem>
<para><note>
- JBoss Messaging 1.4.0 requires a patched version of jboss-remoting.jar. The version is JBoss Remoting 2.2.2.SP4-brew. This version is available on JBoss EAP 4.3, so if you're using a different version you should download it. The patched jar can be found
+ JBoss Messaging 1.4.0 requires a patched version of jboss-remoting.jar. The version is JBoss Remoting 2.2.2.SP7-brew. This version is available on JBoss EAP 4.3, so if you're using a different version you should download it. The patched jar can be found
<ulink
- url="http://repository.jboss.com/jboss/remoting/2.2.2.SP4-brew/lib/">here</ulink>
+ url="http://repository.jboss.com/jboss/remoting/2.2.2.SP7-brew/lib/">here</ulink>
. Please download it and make sure this jar is on your classpath *before* jbossall-client.jar.
</note></para>
</listitem>
More information about the jboss-cvs-commits
mailing list