May 2011 - jboss-remoting-commits

JBoss Remoting SVN: r6364 - remoting2/branches/2.x.

by jboss-remoting-commits＠lists.jboss.org

Author: ron.sigal(a)jboss.com Date: 2011-05-05 23:20:46 -0400 (Thu, 05 May 2011) New Revision: 6364 Modified: remoting2/branches/2.x/build.xml Log: JBREM-1291: Changed AS startup targets to work in linux environment. Modified: remoting2/branches/2.x/build.xml =================================================================== --- remoting2/branches/2.x/build.xml 2011-05-06 03:19:48 UTC (rev 6363) +++ remoting2/branches/2.x/build.xml 2011-05-06 03:20:46 UTC (rev 6364) @@ -1795,7 +1795,7 @@ <target name="AS.start"> <property environment="env"/> <exec executable="${shell}" searchpath="true" dir="${jboss.home}" spawn="true"> - <env key="Path" path="${env.Path}${path.separator}c:/cygwin/usr/bin"/> + <env key="Path" path="${env.Path}${path.separator}${path.extension}"/> <env key="JBOSS_HOME" value="${jboss.home}"/> <arg file="${jboss.home}/bin/run.sh"/> </exec> @@ -1806,7 +1806,7 @@ <target name="AS.start.opts"> <property environment="env"/> <exec executable="${shell}" searchpath="true" dir="${jboss.home}" spawn="true"> - <env key="Path" path="${env.Path}${path.separator}c:/cygwin/usr/bin"/> + <env key="Path" path="${env.Path}${path.separator}${path.extension}"/> <env key="JAVA_OPTS" value="${java.opts}"/> <env key="JBOSS_HOME" value="${jboss.home}"/> <arg file="${jboss.home}/bin/run.sh"/>

12 years, 11 months

1
0
0 / 0

JBoss Remoting SVN: r6363 - remoting2/branches/2.x.

by jboss-remoting-commits＠lists.jboss.org

Author: ron.sigal(a)jboss.com Date: 2011-05-05 23:19:48 -0400 (Thu, 05 May 2011) New Revision: 6363 Modified: remoting2/branches/2.x/local.properties Log: JBREM-1291: Changed some properties for linux environment. Modified: remoting2/branches/2.x/local.properties =================================================================== --- remoting2/branches/2.x/local.properties 2011-05-06 01:49:37 UTC (rev 6362) +++ remoting2/branches/2.x/local.properties 2011-05-06 03:19:48 UTC (rev 6363) @@ -1,5 +1,9 @@ -jboss.home=c://cygwin/home/rsigal/workspace.new/jboss-as-parent-trunk/build/output/jboss-5.0.0.GA -as.startup.time=220 +jboss.home=/home/rsigal/JBoss/JBossAS/jboss-5.1.0.GA +as.startup.time=20 as.shutdown.time=10 -shell=c:/cygwin/bin/sh.exe -findbugs.home=c:/cygwin/opt/local/findbugs-1.3.9 \ No newline at end of file +shell=/bin/sh +path.extension= +# When running in cygwin, use: +# shell=c:/cygwin/bin/sh.exe +# path.extension=c:/cygwin/usr/bin +findbugs.home=/opt/local/findbugs-1.3.9 \ No newline at end of file

12 years, 11 months

1
0
0 / 0

JBoss Remoting SVN: r6362 - remoting2/branches/2.x/docs/userguide/en.

by jboss-remoting-commits＠lists.jboss.org

Author: ron.sigal(a)jboss.com Date: 2011-05-05 21:49:37 -0400 (Thu, 05 May 2011) New Revision: 6362 Modified: remoting2/branches/2.x/docs/userguide/en/chap5.xml Log: JBREM-1275: Added definition of bisocket "secondaryMaxThreads" and "secondaryTimeout" parameters. Modified: remoting2/branches/2.x/docs/userguide/en/chap5.xml =================================================================== --- remoting2/branches/2.x/docs/userguide/en/chap5.xml 2011-05-06 01:27:31 UTC (rev 6361) +++ remoting2/branches/2.x/docs/userguide/en/chap5.xml 2011-05-06 01:49:37 UTC (rev 6362) @@ -40,6 +40,9 @@ failures. Currently, the default values are accepted. </para> + <para><emphasis role="bold">Note.</emphasis> If opening ports on the client side is not a problem, + then JBoss Messaging will run just fine with the somewhat simpler socket transport.</para> + <para>The following bisocket configuration parameters are added to those used in the socket transport: </para> @@ -57,6 +60,14 @@ <para><emphasis role="bold">pingFrequency</emphasis> - the frequency, in milliseconds, with which the server side sends a ping over the control connection. The default value is 5000 milliseconds.</para> + + <para><emphasis role="bold">secondaryMaxThreads</emphasis>: Determines the + maximum number of sockets accepted by the secondary <classname>ServerSocket</classname> + that can be processed simultaneously. Introduced in release 2.5.4.SP2. Default value is 50.</para> + + <para><emphasis role="bold">secondaryTimeout</emphasis>: Determines the timeout used when reading + initial data from a socket accepted by the secondary <classname>ServerSocket</classname>. Introduced in release + 2.5.4.SP2. Default value is 60000 ms.</para> </section>

12 years, 11 months

1
0
0 / 0

JBoss Remoting SVN: r6361 - remoting2/branches/2.2/docs/guide/en.

by jboss-remoting-commits＠lists.jboss.org

Author: ron.sigal(a)jboss.com Date: 2011-05-05 21:27:31 -0400 (Thu, 05 May 2011) New Revision: 6361 Modified: remoting2/branches/2.2/docs/guide/en/chap5.xml Log: JBREM-1275: Added definition of bisocket "secondaryMaxThreads" and "secondaryTimeout" parameters. Modified: remoting2/branches/2.2/docs/guide/en/chap5.xml =================================================================== --- remoting2/branches/2.2/docs/guide/en/chap5.xml 2011-05-06 01:11:12 UTC (rev 6360) +++ remoting2/branches/2.2/docs/guide/en/chap5.xml 2011-05-06 01:27:31 UTC (rev 6361) @@ -2858,7 +2858,42 @@ number of attempts it should make to create both ordinary and control sockets. The default value is 10. </para> - + <para> + <emphasis role="bold">MAX_CONTROL_CONNECTION_RESTARTS</emphasis> + (actual value is "maxControlConnectionRestarts"): The client side uses + this value to limit the number of times it will request a new control + connection after a ping timeout. The default value is 10. + </para> + + <para> + <emphasis role="bold">SECONDARY_BIND_PORT</emphasis> (actual value is + "secondaryBindPort"): The server side uses this parameter to determine + the bind port for the secondary + <classname>ServerSocket</classname>.</para> + + <para> + <emphasis role="bold">SECONDARY_CONNECT_PORT</emphasis> (actual value + is "secondaryConnectPort"): The server side uses this parameter to + determine the connect port used by the client side to connect to the + secondary <classname>ServerSocket</classname>. + </para> + + + <para> + <emphasis role="bold">SECONDARY_MAX_THREADS</emphasis> (actual value + is "secondaryMaxThreads"): Determines the maximum number of + sockets accepted by the secondary <classname>ServerSocket</classname> + that can be processed simultaneously. Introduced in release + 2.2.4. Default value is 50.</para> + + <para> + <emphasis role="bold">SECONDARY_TIMEOUT</emphasis> (actual value + is "secondaryTimeout"): Determines the timeout used when reading + initial data from a socket accepted by the secondary + <classname>ServerSocket</classname>. Introduced in release + 2.2.4. Default value is 60000 ms. + </para> + <para>Also, the parameter "acceptThreadPriorityIncrement", inherited from <classname>org.jboss.remoting.transport.socket.SocketServerInvoker</classname>, can be used to increment the priority of the thread that manages the secondary @@ -6619,6 +6654,21 @@ determine the connect port used by the client side to connect to the secondary <classname>ServerSocket</classname>.</para> + <para> + <emphasis role="bold">SECONDARY_MAX_THREADS</emphasis> (actual value + is "secondaryMaxThreads"): Determines the maximum number of + sockets accepted by the secondary <classname>ServerSocket</classname> + that can be processed simultaneously. Introduced in release + 2.2.4. Default value is 50.</para> + + <para> + <emphasis role="bold">SECONDARY_TIMEOUT</emphasis> (actual value + is "secondaryTimeout"): Determines the timeout used when reading + initial data from a socket accepted by the secondary + <classname>ServerSocket</classname>. Introduced in release + 2.2.4. Default value is 60000 ms. + </para> + <bridgehead>org.jboss.remoting.transport.http.HTTPMetadataConstants</bridgehead> <para>The following are keys to use to get corresponding values from the

12 years, 11 months

1
0
0 / 0

JBoss Remoting SVN: r6360 - remoting2/branches/2.x/docs/guide/en.

by jboss-remoting-commits＠lists.jboss.org

Author: ron.sigal(a)jboss.com Date: 2011-05-05 21:11:12 -0400 (Thu, 05 May 2011) New Revision: 6360 Modified: remoting2/branches/2.x/docs/guide/en/chap5.xml Log: JBREM-1275: Added definition of bisocket "secondaryMaxThreads" and "secondaryTimeout" parameters. Modified: remoting2/branches/2.x/docs/guide/en/chap5.xml =================================================================== --- remoting2/branches/2.x/docs/guide/en/chap5.xml 2011-05-05 04:48:41 UTC (rev 6359) +++ remoting2/branches/2.x/docs/guide/en/chap5.xml 2011-05-06 01:11:12 UTC (rev 6360) @@ -2493,7 +2493,22 @@ determine the connect ports used by the client side to connect to the secondary <classname>ServerSocket</classname>s in a multihome server.</para> + + <para> + <emphasis role="bold">SECONDARY_MAX_THREADS</emphasis> (actual value + is "secondaryMaxThreads"): Determines the maximum number of + sockets accepted by the secondary <classname>ServerSocket</classname> + that can be processed simultaneously. Introduced in release + 2.5.4.SP2. Default value is 50.</para> + <para> + <emphasis role="bold">SECONDARY_TIMEOUT</emphasis> (actual value + is "secondaryTimeout"): Determines the timeout used when reading + initial data from a socket accepted by the secondary + <classname>ServerSocket</classname>. Introduced in release + 2.5.4.SP2. Default value is 60000 ms. + </para> + <para>Also, the parameter "acceptThreadPriorityIncrement", inherited from <classname>org.jboss.remoting.transport.socket.SocketServerInvoker</classname>, can be used to increment the priority of the thread that manages the secondary @@ -6590,7 +6605,22 @@ determine the connect ports used by the client side to connect to the secondary <classname>ServerSocket</classname>s in a multihome server.</para> - + + <para> + <emphasis role="bold">SECONDARY_MAX_THREADS</emphasis> (actual value + is "secondaryMaxThreads"): Determines the maximum number of + sockets accepted by the secondary <classname>ServerSocket</classname> + that can be processed simultaneously. Introduced in release + 2.5.4.SP2. Default value is 50.</para> + + <para> + <emphasis role="bold">SECONDARY_TIMEOUT</emphasis> (actual value + is "secondaryTimeout"): Determines the timeout used when reading + initial data from a socket accepted by the secondary + <classname>ServerSocket</classname>. Introduced in release + 2.5.4.SP2. Default value is 60000 ms. + </para> + </section> <section>

12 years, 11 months

1
0
0 / 0

JBoss Remoting SVN: r6359 - remoting2/branches/2.x/docs/guide/en.

by jboss-remoting-commits＠lists.jboss.org

Author: ron.sigal(a)jboss.com Date: 2011-05-05 00:48:41 -0400 (Thu, 05 May 2011) New Revision: 6359 Modified: remoting2/branches/2.x/docs/guide/en/chap17.xml Log: JBREM-1291: Added 2.5.4.SP2 release notes. Modified: remoting2/branches/2.x/docs/guide/en/chap17.xml =================================================================== --- remoting2/branches/2.x/docs/guide/en/chap17.xml 2011-05-05 04:42:12 UTC (rev 6358) +++ remoting2/branches/2.x/docs/guide/en/chap17.xml 2011-05-05 04:48:41 UTC (rev 6359) @@ -70,6 +70,29 @@ <section> <title>Version 2.5</title> + <bridgehead>Release Notes - JBoss Remoting - Version 2.5.4.SP2 (Flounder)</bridgehead> + + <para><emphasis role="bold">Bug</emphasis></para> + + <para>* [JBREM-1276] - SecondaryServerSocketThread should catch java.lang.Error</para> + <para>* [JBREM-1282] - ServerInvoker does not close StreamHandler in the case of "addstreamcallback"</para> + <para>* [JBREM-1285] - Callback Connector for in-jvm connection should create a LocalServerInvoker</para> + <para>* [JBREM-1288] - StreamServer for in-jvm connection should create a LocalServerInvoker</para> + + <para><emphasis role="bold">Enhancement</emphasis></para> + + <para>* [JBREM-1275] - Make maxthreads, timeout configurable in BisocketServerInvoker.SecondaryServerSocketThread</para> + <para>* [JBREM-1277] - Allow configuration of socket and bisocket accept thread priority</para> + <para>* [JBREM-1283] - CLONE [JBREM-1281] - Support setting executor in CoyoteInvoker</para> + + <para><emphasis role="bold">Release</emphasis></para> + + <para>* [JBREM-1291] - Release 2.5.4.SP2</para> + + <para><emphasis role="bold">Task</emphasis></para> + + <para>* [JBREM-1290] - Assure version compatibility with earlier versions of Remoting</para> + <bridgehead>Release Notes - JBoss Remoting - Version 2.5.4.SP1 (Flounder)</bridgehead> <para><emphasis role="bold">Bug</emphasis></para>

12 years, 12 months

1
0
0 / 0

JBoss Remoting SVN: r6358 - remoting2/branches/2.x/docs/guide/en.

by jboss-remoting-commits＠lists.jboss.org

Author: ron.sigal(a)jboss.com Date: 2011-05-05 00:42:12 -0400 (Thu, 05 May 2011) New Revision: 6358 Modified: remoting2/branches/2.x/docs/guide/en/chap1.xml Log: JBREM-1291: Added description of 2.5.4.SP2 features. Modified: remoting2/branches/2.x/docs/guide/en/chap1.xml =================================================================== --- remoting2/branches/2.x/docs/guide/en/chap1.xml 2011-05-05 04:37:27 UTC (rev 6357) +++ remoting2/branches/2.x/docs/guide/en/chap1.xml 2011-05-05 04:42:12 UTC (rev 6358) @@ -189,6 +189,21 @@ support jdk 1.4.</para> <section> + <title>Release 2.5.4.SP2</title> + <itemizedlist> + <listitem> + <para>Ability to increase accept thread priority in socket and bisocket transports</para> + </listitem> + <listitem> + <para>Additional configurability for bisocket transport</para> + </listitem> + <listitem> + <para>Multiple bug fixes</para> + </listitem> + </itemizedlist> + </section> + + <section> <title>Release 2.5.4.SP1</title> <itemizedlist> <listitem>

12 years, 12 months

1
0
0 / 0

JBoss Remoting SVN: r6357 - remoting2/branches/2.x/docs/guide/en.

by jboss-remoting-commits＠lists.jboss.org

Author: ron.sigal(a)jboss.com Date: 2011-05-05 00:37:27 -0400 (Thu, 05 May 2011) New Revision: 6357 Modified: remoting2/branches/2.x/docs/guide/en/master.xml Log: JBREM-1291: Updated version to 2.5.4.SP2. Modified: remoting2/branches/2.x/docs/guide/en/master.xml =================================================================== --- remoting2/branches/2.x/docs/guide/en/master.xml 2011-05-05 04:36:41 UTC (rev 6356) +++ remoting2/branches/2.x/docs/guide/en/master.xml 2011-05-05 04:37:27 UTC (rev 6357) @@ -24,9 +24,9 @@ <bookinfo> <title>JBoss Remoting Guide</title> - <subtitle>JBoss Remoting version 2.5.4.SP1</subtitle> + <subtitle>JBoss Remoting version 2.5.4.SP2</subtitle> - <releaseinfo>February 23, 2011</releaseinfo> + <releaseinfo>May 5, 2011</releaseinfo> <mediaobject> <imageobject>

12 years, 12 months

1
0
0 / 0

JBoss Remoting SVN: r6356 - remoting2/branches/2.x/docs.

by jboss-remoting-commits＠lists.jboss.org

Author: ron.sigal(a)jboss.com Date: 2011-05-05 00:36:41 -0400 (Thu, 05 May 2011) New Revision: 6356 Modified: remoting2/branches/2.x/docs/README.txt Log: JBREM-1291: Added 2.5.4.SP2 release notes. Modified: remoting2/branches/2.x/docs/README.txt =================================================================== --- remoting2/branches/2.x/docs/README.txt 2011-05-05 04:34:36 UTC (rev 6355) +++ remoting2/branches/2.x/docs/README.txt 2011-05-05 04:36:41 UTC (rev 6356) @@ -1,5 +1,5 @@ -JBoss Remoting 2.5.4.SP1 -February 23, 2011 +JBoss Remoting 2.5.4.SP2 +May 5, 2011 This distribution of JBoss Remoting contains the following directories: @@ -41,6 +41,30 @@ ========================================================================================================== ========================================================================================================== +Release Notes - JBoss Remoting - Version 2.5.4.SP2 + +Bug + + * [JBREM-1276] - SecondaryServerSocketThread should catch java.lang.Error + * [JBREM-1282] - ServerInvoker does not close StreamHandler in the case of "addstreamcallback" + * [JBREM-1285] - Callback Connector for in-jvm connection should create a LocalServerInvoker + * [JBREM-1288] - StreamServer for in-jvm connection should create a LocalServerInvoker + +Enhancement + + * [JBREM-1275] - Make maxthreads, timeout configurable in BisocketServerInvoker.SecondaryServerSocketThread + * [JBREM-1277] - Allow configuration of socket and bisocket accept thread priority + * [JBREM-1283] - CLONE [JBREM-1281] - Support setting executor in CoyoteInvoker + +Release + + * [JBREM-1291] - Release 2.5.4.SP2 + +Task + + * [JBREM-1290] - Assure version compatibility with earlier versions of Remoting + +========================================================================================================== Release Notes - JBoss Remoting - Version 2.5.4.SP1 - HTML format Bug

12 years, 12 months

1
0
0 / 0

JBoss Remoting SVN: r6355 - remoting2/branches/2.x.

by jboss-remoting-commits＠lists.jboss.org

Author: ron.sigal(a)jboss.com Date: 2011-05-05 00:34:36 -0400 (Thu, 05 May 2011) New Revision: 6355 Modified: remoting2/branches/2.x/build.xml Log: JBREM-1291: Updated version to 2.5.4.SP2. Modified: remoting2/branches/2.x/build.xml =================================================================== --- remoting2/branches/2.x/build.xml 2011-05-05 03:25:04 UTC (rev 6354) +++ remoting2/branches/2.x/build.xml 2011-05-05 04:34:36 UTC (rev 6355) @@ -225,9 +225,9 @@  <property name="module.name" value="remoting"/> <property name="module.Name" value="JBoss Remoting"/> - <property name="module.version" value="2.5.4.SP1"/> + <property name="module.version" value="2.5.4.SP2"/>  - <property name="module.version.extension" value="2_5_4_SP1"/> + <property name="module.version.extension" value="2_5_4_SP2"/> <property name="implementation.url" value="http://www.jboss.org/products/remoting"/> <property name="root.dir" value="${basedir}"/>

12 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-commits May 2011