[jboss-cvs] JBoss Messaging SVN: r8557 - branches/Branch_1_4/integration/EAP5/etc/remoting.

[jboss-cvs-commits at lists.jboss.org]

Author: dgrove_redhat.com
Date: 2012-07-23 13:45:39 -0400 (Mon, 23 Jul 2012)
New Revision: 8557

Modified:
   branches/Branch_1_4/integration/EAP5/etc/remoting/remoting-bisocket-service.xml
Log:


Modified: branches/Branch_1_4/integration/EAP5/etc/remoting/remoting-bisocket-service.xml
===================================================================
--- branches/Branch_1_4/integration/EAP5/etc/remoting/remoting-bisocket-service.xml	2012-07-23 10:49:35 UTC (rev 8556)
+++ branches/Branch_1_4/integration/EAP5/etc/remoting/remoting-bisocket-service.xml	2012-07-23 17:45:39 UTC (rev 8557)
@@ -32,8 +32,8 @@
 
                <!-- End immutable parameters -->
 
-               <!-- the following parameters are useful when there is a firewall between client and server. Adjust the values 
-                    to suit your environment.
+               <!--  
+                   These ping parameters are used to keep the control channel open.
                     
                     numberOfCallRetries: Perhaps better named "numberOfCallTrys" as the first contact attempt is counted.  So
                     a value of 2 is the first attempt and one retry.  Note that in most environments, if the first retry does not 
@@ -43,12 +43,10 @@
                     
                     pingWindowFactor: the server waits pingFrequency * pingWindowFactor for a ping reply
                -->                              
-			   <!--
                <attribute name="numberOfCallRetries" isParam="true">2</attribute>
                <attribute name="pingFrequency" isParam="true">30000</attribute>
-               <attribute name="pingWindowFactor" isParam="true">2</attribute>
+               <attribute name="pingWindowFactor" isParam="true">10</attribute>
                <attribute name="generalizeSocketException" isParam="true">true</attribute>
-               -->
 
                <!-- If this attribute is set to "true" then remoting will attempt to round-trip a single
                     byte in order to test the networking connection on every request.  While this is a