March 2011 - jboss-remoting-commits

JBoss Remoting SVN: r6304 - remoting2/tags.

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

Author: ron.sigal(a)jboss.com Date: 2011-03-22 23:23:49 -0400 (Tue, 22 Mar 2011) New Revision: 6304 Added: remoting2/tags/2.2.4/ Log:

13 years, 8 months

1
0
0 / 0

JBoss Remoting SVN: r6303 - remoting2/branches/2.2/src/main/org/jboss/remoting.

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

Author: ron.sigal(a)jboss.com Date: 2011-03-22 22:19:38 -0400 (Tue, 22 Mar 2011) New Revision: 6303 Modified: remoting2/branches/2.2/src/main/org/jboss/remoting/Version.java Log: JBREM-1264: Changed version to 2.2.4. Modified: remoting2/branches/2.2/src/main/org/jboss/remoting/Version.java =================================================================== --- remoting2/branches/2.2/src/main/org/jboss/remoting/Version.java 2011-03-23 02:12:42 UTC (rev 6302) +++ remoting2/branches/2.2/src/main/org/jboss/remoting/Version.java 2011-03-23 02:19:38 UTC (rev 6303) @@ -36,7 +36,7 @@ public static final byte VERSION_2 = 2; public static final byte VERSION_2_2 = 22; - public static final String VERSION = "2.2.3.SP4"; + public static final String VERSION = "2.2.4"; private static final byte byteVersion = VERSION_2_2; private static byte defaultByteVersion = byteVersion; private static boolean performVersioning = true;

13 years, 8 months

1
0
0 / 0

JBoss Remoting SVN: r6302 - remoting2/branches/2.2.

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

Author: ron.sigal(a)jboss.com Date: 2011-03-22 22:12:42 -0400 (Tue, 22 Mar 2011) New Revision: 6302 Modified: remoting2/branches/2.2/build.xml Log: JBREM-1264: Updated version and added release 2.2.3.SP3 to versioning tests. Modified: remoting2/branches/2.2/build.xml =================================================================== --- remoting2/branches/2.2/build.xml 2011-03-23 02:09:19 UTC (rev 6301) +++ remoting2/branches/2.2/build.xml 2011-03-23 02:12:42 UTC (rev 6302) @@ -83,9 +83,9 @@  <property name="module.name" value="remoting"/> <property name="module.Name" value="JBoss Remoting"/> - <property name="module.version" value="2.2.3.SP3"/> + <property name="module.version" value="2.2.4"/>  - <property name="module.version.extension" value="2_2_3_SP3"/> + <property name="module.version.extension" value="2_2_4"/> <property name="implementation.url" value="http://www.jboss.org/products/remoting"/> <property name="root.dir" value="${basedir}"/> @@ -682,7 +682,7 @@ </target> <target name="tests.functional.core" depends="configure"> - <antcall target="tests.functional.serialization.java.core" inheritrefs="true"/> +  <antcall target="tests.functional.serialization.jboss.core" inheritrefs="true"/> </target> @@ -1040,7 +1040,10 @@  <target name="get-jvm"> <condition property="isJDK5"> - <equals arg1="${ant.java.version}" arg2="1.5"/> + <or> + <equals arg1="${ant.java.version}" arg2="1.5"/> + <equals arg1="${ant.java.version}" arg2="1.6"/> + </or> </condition> </target> @@ -1672,8 +1675,35 @@ <param name="clientImplementsServerIdentity" value="true"/> <param name="serverImplementsServerIdentity" value="true"/> </antcall> - +  +  + <antcall target="tests.versioning.all_transports" inheritrefs="true"> + <param name="jboss-junit-configuration" value="2_2_3_SP3-client"/> + <param name="client.classpath" value="${etc.dir}/lib/remoting_2_2_3_SP3/jboss-remoting.jar"/> + <param name="server.classpath" value="${output.lib.dir}/jboss-remoting.jar"/> + <param name="client.pre_2_0_compatible" value=""/> + <param name="server.pre_2_0_compatible" value=""/> + <param name="client.version" value=""/> + <param name="server.version" value="2"/> + <param name="check_connection" value="false"/> + <param name="clientImplementsServerIdentity" value="false"/> + <param name="serverImplementsServerIdentity" value="true"/> + </antcall> + <antcall target="tests.versioning.all_transports" inheritrefs="true"> + <param name="jboss-junit-configuration" value="2_2_3_SP3-server"/> + <param name="server.classpath" value="${etc.dir}/lib/remoting_2_2_3_SP3/jboss-remoting.jar"/> + <param name="client.classpath" value="${output.lib.dir}/jboss-remoting.jar"/> + <param name="client.pre_2_0_compatible" value=""/> + <param name="server.pre_2_0_compatible" value=""/> + <param name="client.version" value="2"/> + <param name="server.version" value=""/> + <param name="check_connection" value="false"/> + <param name="clientImplementsServerIdentity" value="true"/> + <param name="serverImplementsServerIdentity" value="false"/> + </antcall> + +   <antcall target="tests.versioning.all_transports" inheritrefs="true"> <param name="jboss-junit-configuration" value="2_2_3_SP2-client"/>

13 years, 8 months

1
0
0 / 0

JBoss Remoting SVN: r6301 - in remoting2/branches/2.2/src/etc/lib: remoting_2_2_3_SP3 and 1 other directory.

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

Author: ron.sigal(a)jboss.com Date: 2011-03-22 22:09:19 -0400 (Tue, 22 Mar 2011) New Revision: 6301 Added: remoting2/branches/2.2/src/etc/lib/remoting_2_2_3_SP3/ remoting2/branches/2.2/src/etc/lib/remoting_2_2_3_SP3/jboss-remoting.jar Log: JBREM-1278: Added jboss-remoting.jar from release 2.2.3.SP3. Added: remoting2/branches/2.2/src/etc/lib/remoting_2_2_3_SP3/jboss-remoting.jar =================================================================== (Binary files differ) Property changes on: remoting2/branches/2.2/src/etc/lib/remoting_2_2_3_SP3/jboss-remoting.jar ___________________________________________________________________ Added: svn:mime-type + application/octet-stream

13 years, 8 months

1
0
0 / 0

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

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

Author: ron.sigal(a)jboss.com Date: 2011-03-22 22:05:42 -0400 (Tue, 22 Mar 2011) New Revision: 6300 Modified: remoting2/branches/2.2/docs/guide/en/chap1.xml remoting2/branches/2.2/docs/guide/en/chap16.xml remoting2/branches/2.2/docs/guide/en/master.xml Log: JBREM-1264: Included 2.2.4 release notes. Modified: remoting2/branches/2.2/docs/guide/en/chap1.xml =================================================================== --- remoting2/branches/2.2/docs/guide/en/chap1.xml 2011-03-23 01:43:51 UTC (rev 6299) +++ remoting2/branches/2.2/docs/guide/en/chap1.xml 2011-03-23 02:05:42 UTC (rev 6300) @@ -182,6 +182,21 @@ <title>What's new?</title> <section> + <title>Release 2.2.4</title> + <itemizedlist> + <listitem> + <para>New server identity feature</para> + </listitem> + <listitem> + <para>New configuration parameters</para> + </listitem> + <listitem> + <para>Multiple enhancements and bug fixes</para> + </listitem> + </itemizedlist> + </section> + + <section> <title>In release 2.2.3.SP3</title> <orderedlist> Modified: remoting2/branches/2.2/docs/guide/en/chap16.xml =================================================================== --- remoting2/branches/2.2/docs/guide/en/chap16.xml 2011-03-23 01:43:51 UTC (rev 6299) +++ remoting2/branches/2.2/docs/guide/en/chap16.xml 2011-03-23 02:05:42 UTC (rev 6300) @@ -17,6 +17,40 @@ <para></para> <para>==========================================================================================================</para> +<para>Release Notes - JBoss Remoting - Version 2.2.4</para> + +<para>Bug</para> + + <para>* [JBREM-1242] - Fix deadlock between Client and MicroRemoteClientInvoker</para> + <para>* [JBREM-1261] - Prevent DOS attack on BisocketServerInvoker$SecondaryServerSocketThread</para> + <para>* [JBREM-1268] - RemoteClientInvoker can change configuration map and prevent InvokerRegistry from reusing client invokers</para> + <para>* [JBREM-1269] - Fix deadlock between Client and MicroRemoteClientInvoker, part 2</para> + <para>* [JBREM-1276] - SecondaryServerSocketThread should catch java.lang.Error</para> + +<para>Enhancement</para> + + <para>* [JBREM-1245] - Consider javax.net.ssl.SSLException("Connection has been shutdown") to be retriable</para> + <para>* [JBREM-1248] - Avoid connecting to a server in catch clause in case of HttpClientInvoker connection failure</para> + <para>* [JBREM-1262] - Consider java.io.IOException("Software caused connection abort: socket write error") retriable</para> + <para>* [JBREM-1263] - ClientSocketWrapper.checkConnection() should check returned value</para> + <para>* [JBREM-1267] - Allow HTTPClientInvoker to call disconnect on HttpURLConnection after use</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>Feature Request</para> + + <para>* [JBREM-1144] - Extend connection identity to server side</para> + +<para>Release</para> + + <para>* [JBREM-1264] - Release 2.2.4</para> + +<para>Task</para> + + <para>* [JBREM-1272] - Remove JBoss.ORG EULA file</para> + <para>* [JBREM-1278] - Assure version compatibility with earlier versions of Remoting</para> + +<para>==========================================================================================================</para> <para>Release Notes - JBoss Remoting - Version 2.2.3.SP3</para> <para>Bug</para> Modified: remoting2/branches/2.2/docs/guide/en/master.xml =================================================================== --- remoting2/branches/2.2/docs/guide/en/master.xml 2011-03-23 01:43:51 UTC (rev 6299) +++ remoting2/branches/2.2/docs/guide/en/master.xml 2011-03-23 02:05:42 UTC (rev 6300) @@ -23,9 +23,9 @@ <bookinfo> <title>JBoss Remoting Guide</title> - <subtitle>JBoss Remoting version 2.2.3.SP3</subtitle> + <subtitle>JBoss Remoting version 2.2.4</subtitle> - <releaseinfo>August 4, 2010</releaseinfo> + <releaseinfo>March 23, 2011</releaseinfo> <mediaobject> <imageobject> @@ -34,7 +34,7 @@ </mediaobject> <copyright> - <year>2010 JBoss by Red Hat</year> + <year>2011 JBoss by Red Hat</year> <holder>.</holder> </copyright>

13 years, 8 months

1
0
0 / 0

JBoss Remoting SVN: r6299 - remoting2/branches/2.2/docs.

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

Author: ron.sigal(a)jboss.com Date: 2011-03-22 21:43:51 -0400 (Tue, 22 Mar 2011) New Revision: 6299 Modified: remoting2/branches/2.2/docs/README.txt Log: JBREM-1264: Added release notes for release 2.2.4. Modified: remoting2/branches/2.2/docs/README.txt =================================================================== --- remoting2/branches/2.2/docs/README.txt 2011-03-22 22:46:43 UTC (rev 6298) +++ remoting2/branches/2.2/docs/README.txt 2011-03-23 01:43:51 UTC (rev 6299) @@ -1,5 +1,5 @@ -JBoss Remoting 2.2.3.SP2 -February 21, 2010 +JBoss Remoting 2.2.4 +March 23, 2011 This distribution of JBoss Remoting contains the following directories: @@ -25,7 +25,42 @@ Current issues can be found within the JBoss Remoting project on Jira (http://jira.jboss.com). If you find a bug or issue that is not already in Jira, please create one. + ========================================================================================================== +Release Notes - JBoss Remoting - Version 2.2.4 + +Bug + + * [JBREM-1242] - Fix deadlock between Client and MicroRemoteClientInvoker + * [JBREM-1261] - Prevent DOS attack on BisocketServerInvoker$SecondaryServerSocketThread + * [JBREM-1268] - RemoteClientInvoker can change configuration map and prevent InvokerRegistry from reusing client invokers + * [JBREM-1269] - Fix deadlock between Client and MicroRemoteClientInvoker, part 2 + * [JBREM-1276] - SecondaryServerSocketThread should catch java.lang.Error + +Enhancement + + * [JBREM-1245] - Consider javax.net.ssl.SSLException("Connection has been shutdown") to be retriable + * [JBREM-1248] - Avoid connecting to a server in catch clause in case of HttpClientInvoker connection failure + * [JBREM-1262] - Consider java.io.IOException("Software caused connection abort: socket write error") retriable + * [JBREM-1263] - ClientSocketWrapper.checkConnection() should check returned value + * [JBREM-1267] - Allow HTTPClientInvoker to call disconnect on HttpURLConnection after use + * [JBREM-1275] - Make maxthreads, timeout configurable in BisocketServerInvoker.SecondaryServerSocketThread + * [JBREM-1277] - Allow configuration of socket and bisocket accept thread priority + +Feature Request + + * [JBREM-1144] - Extend connection identity to server side + +Release + + * [JBREM-1264] - Release 2.2.4 + +Task + + * [JBREM-1272] - Remove JBoss.ORG EULA file + * [JBREM-1278] - Assure version compatibility with earlier versions of Remoting + +========================================================================================================== Release Notes - JBoss Remoting - Version 2.2.3.SP3 Bug

13 years, 8 months

1
0
0 / 0

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

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

Author: ron.sigal(a)jboss.com Date: 2011-03-22 18:46:43 -0400 (Tue, 22 Mar 2011) New Revision: 6298 Modified: remoting2/branches/2.x/docs/userguide/en/chap4.xml remoting2/branches/2.x/docs/userguide/en/chap5.xml Log: JBREM-1277: Added references to "acceptThreadPriorityIncrement" parameter. Modified: remoting2/branches/2.x/docs/userguide/en/chap4.xml =================================================================== --- remoting2/branches/2.x/docs/userguide/en/chap4.xml 2011-03-22 19:53:11 UTC (rev 6297) +++ remoting2/branches/2.x/docs/userguide/en/chap4.xml 2011-03-22 22:46:43 UTC (rev 6298) @@ -44,6 +44,15 @@ <section> <title>Server side parameters</title> + <para><emphasis role="bold">acceptThreadPriorityIncrement</emphasis> - can + be used to increment the priority of the accept thread, which manages the + <classname>ServerSocket</classname>. The value is added to + <code>java.lang.Thread.NORM_PRIORITY</code>, and the resulting value must be + no more than <code>java.lang.Thread.MAX_PRIORITY</code>. This parameter might + be useful on a heavily loaded machine if the accept + thread is getting starved. Introduced in release 2.5.4.SP2. + </para> + <para><emphasis role="bold">backlog</emphasis> - the preferred number of unaccepted incoming connections allowed at a given time. The actual number may be greater than the specified backlog. When the queue is Modified: remoting2/branches/2.x/docs/userguide/en/chap5.xml =================================================================== --- remoting2/branches/2.x/docs/userguide/en/chap5.xml 2011-03-22 19:53:11 UTC (rev 6297) +++ remoting2/branches/2.x/docs/userguide/en/chap5.xml 2011-03-22 22:46:43 UTC (rev 6298) @@ -46,6 +46,15 @@ <section> <title>Server side parameters</title> + <para><emphasis role="bold">acceptThreadPriorityIncrement</emphasis> - can + be used to increment the priority of the thread which manages the secondary + <classname>ServerSocket</classname> (as well as the thread that manages the primary + <classname>ServerSocket</classname> in the socket transport). The value is added to + <code>java.lang.Thread.NORM_PRIORITY</code>, and the resulting value must be + no more than <code>java.lang.Thread.MAX_PRIORITY</code>. This parameter might + be useful on a heavily loaded machine if the accept + thread is getting starved. Introduced in release 2.5.4.SP2.</para> + <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>

13 years, 8 months

1
0
0 / 0

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

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

Author: ron.sigal(a)jboss.com Date: 2011-03-22 15:53:11 -0400 (Tue, 22 Mar 2011) New Revision: 6297 Modified: remoting2/branches/2.2/docs/guide/en/chap5.xml Log: JBREM-1277: Added discussion of "acceptThreadPriorityIncrement" parameter. Modified: remoting2/branches/2.2/docs/guide/en/chap5.xml =================================================================== --- remoting2/branches/2.2/docs/guide/en/chap5.xml 2011-03-22 19:42:23 UTC (rev 6296) +++ remoting2/branches/2.2/docs/guide/en/chap5.xml 2011-03-22 19:53:11 UTC (rev 6297) @@ -1078,6 +1078,16 @@ <classname>java.net.SocketTimeoutException</classname>. If set to "true", or if JBossSerialization is being used, the server thread will continue to wait for an invocation; otherwise, it will return itself to the thread pool.</para> + + + <para><emphasis role="bold">acceptThreadPriorityIncrement</emphasis> - can + be used to increment the priority of the accept thread, which manages the + <classname>ServerSocket</classname>. The value is added to + <code>java.lang.Thread.NORM_PRIORITY</code>, and the resulting value must be + no more than <code>java.lang.Thread.MAX_PRIORITY</code>. This parameter might + be useful on a heavily loaded machine if the accept + thread is getting starved. + </para> <bridgehead>Configurations affecting the Socket invoker client</bridgehead> @@ -2847,6 +2857,18 @@ <classname>BisocketServerInvoker</classname> uses it to govern the number of attempts it should make to create both ordinary and control sockets. The default value is 10. </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 + <classname>ServerSocket</classname>. The value is added to + <code>java.lang.Thread.NORM_PRIORITY</code>, and the resulting value must be + no more than <code>java.lang.Thread.MAX_PRIORITY</code>. This parameter might + be useful on a heavily loaded machine if the secondary <classname>ServerSocket</classname> + thread is getting starved. + </para> + </section> <section> @@ -6821,6 +6843,18 @@ value is 'serverSocketClass') - specifies the fully qualified class name for the custom SocketWrapper implementation to use on the server.</para> + + <para><emphasis role="bold">Bean properties (meaning have getter/setter):</emphasis></para> + + <para><emphasis role="bold">acceptThreadPriorityIncrement</emphasis> - can + be used to increment the priority of the accept thread, which manages the + <classname>ServerSocket</classname>. The value is added to + <code>java.lang.Thread.NORM_PRIORITY</code>, and the resulting value must be + no more than <code>java.lang.Thread.MAX_PRIORITY</code>. This parameter might + be useful on a heavily loaded machine if the accept + thread is getting starved. + </para> + <bridgehead>org.jboss.remoting.transport.socket.SocketWrapper</bridgehead> <para><emphasis role="bold">WRITE_TIMEOUT</emphasis> (actual value

13 years, 8 months

1
0
0 / 0

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

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

Author: ron.sigal(a)jboss.com Date: 2011-03-22 15:42:23 -0400 (Tue, 22 Mar 2011) New Revision: 6296 Modified: remoting2/branches/2.x/docs/guide/en/chap5.xml Log: JBREM-1277: Added discussion about "acceptThreadPriorityIncrement". Modified: remoting2/branches/2.x/docs/guide/en/chap5.xml =================================================================== --- remoting2/branches/2.x/docs/guide/en/chap5.xml 2011-03-22 19:12:42 UTC (rev 6295) +++ remoting2/branches/2.x/docs/guide/en/chap5.xml 2011-03-22 19:42:23 UTC (rev 6296) @@ -1637,6 +1637,15 @@ all <classname>ServerThread</classname>s are shut down immediately, even if they are processing an invocation.</para> + <para><emphasis role="bold">acceptThreadPriorityIncrement</emphasis> - can + be used to increment the priority of the accept thread, which manages the + <classname>ServerSocket</classname>. The value is added to + <code>java.lang.Thread.NORM_PRIORITY</code>, and the resulting value must be + no more than <code>java.lang.Thread.MAX_PRIORITY</code>. This parameter might + be useful on a heavily loaded machine if the accept + thread is getting starved. + </para> + <bridgehead>Configurations affecting the Socket invoker client</bridgehead> @@ -2471,6 +2480,16 @@ secondary <classname>ServerSocket</classname>s in a multihome server.</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 + <classname>ServerSocket</classname>. The value is added to + <code>java.lang.Thread.NORM_PRIORITY</code>, and the resulting value must be + no more than <code>java.lang.Thread.MAX_PRIORITY</code>. This parameter might + be useful on a heavily loaded machine if the secondary <classname>ServerSocket</classname> + thread is getting starved. + </para> + </section> <section> @@ -6822,11 +6841,20 @@ <para><emphasis role="bold">Bean properties (meaning have getter/setter):</emphasis></para> + <para><emphasis role="bold">acceptThreadPriorityIncrement</emphasis> - can + be used to increment the priority of the accept thread, which manages the + <classname>ServerSocket</classname>. The value is added to + <code>java.lang.Thread.NORM_PRIORITY</code>, and the resulting value must be + no more than <code>java.lang.Thread.MAX_PRIORITY</code>. This parameter might + be useful on a heavily loaded machine if the accept + thread is getting starved. + </para> + <para><emphasis role="bold">ImmediateShutdown</emphasis> - a flag for indicating that <classname>SocketServerInvoker</classname> should shut down all of its <classname>ServerThreads</classname> immediately instead of waiting for any current invocations to finish.</para> - + </section> <section>

13 years, 8 months

1
0
0 / 0

JBoss Remoting SVN: r6295 - remoting2/branches/2.x/src/main/org/jboss/remoting/transport/bisocket.

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

Author: ron.sigal(a)jboss.com Date: 2011-03-22 15:12:42 -0400 (Tue, 22 Mar 2011) New Revision: 6295 Modified: remoting2/branches/2.x/src/main/org/jboss/remoting/transport/bisocket/BisocketServerInvoker.java Log: JBREM-1276: Added catch clause for Error. Modified: remoting2/branches/2.x/src/main/org/jboss/remoting/transport/bisocket/BisocketServerInvoker.java =================================================================== --- remoting2/branches/2.x/src/main/org/jboss/remoting/transport/bisocket/BisocketServerInvoker.java 2011-03-22 19:10:47 UTC (rev 6294) +++ remoting2/branches/2.x/src/main/org/jboss/remoting/transport/bisocket/BisocketServerInvoker.java 2011-03-22 19:12:42 UTC (rev 6295) @@ -1202,8 +1202,14 @@ log.error("Failed to accept socket connection", e); else return; - } + catch (Error e) + { + if (running) + log.error("error", e); + else + return; + } } }

13 years, 8 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 March 2011