Author: ron.sigal(a)jboss.com Date: 2009-09-02 18:54:56 -0400 (Wed, 02 Sep 2009) New Revision: 5435 Modified: remoting2/branches/2.2/docs/guide/en/chap5.xml Log: JBREM-1107: Added comment about IdleTimeoutTask bug. Modified: remoting2/branches/2.2/docs/guide/en/chap5.xml =================================================================== --- remoting2/branches/2.2/docs/guide/en/chap5.xml 2009-09-02 19:29:31 UTC (rev 5434) +++ remoting2/branches/2.2/docs/guide/en/chap5.xml 2009-09-02 22:54:56 UTC (rev 5435) @@ -1228,6 +1228,14 @@ finished processing on a particular socket connection and have been returned to the thread pool for later reuse. </para> + <para><emphasis role="bold">Note.</emphasis> Prior to release 2.2.3.SP1, + a bug allowed the termination of server threads in the middle of a long + invocation. If the idle timeout facility is used, upgrading is strongly + recommended. Note that even with the bug fix, a server thread that is + engaged in a long invocation when the idle timeout checker is activated + can be marked for destruction after the invocation is complete. The + "idleTimeout" value should be configured accordingly.</para> + <para><emphasis role="bold">Note.</emphasis> Prior to release 2.2.2.SP7, if a server thread experienced a <classname>java.net.SocketTimeoutException</classname>, it would return