Author: timfox
Date: 2009-09-28 14:08:09 -0400 (Mon, 28 Sep 2009)
New Revision: 8003
Modified:
trunk/docs/user-manual/en/configuration-index.xml
trunk/docs/user-manual/en/connection-ttl.xml
Log:
changed default connection ttl in docs to 1 minute
Modified: trunk/docs/user-manual/en/configuration-index.xml
===================================================================
--- trunk/docs/user-manual/en/configuration-index.xml 2009-09-28 17:24:07 UTC (rev 8002)
+++ trunk/docs/user-manual/en/configuration-index.xml 2009-09-28 18:08:09 UTC (rev 8003)
@@ -871,7 +871,7 @@
connection-factory.connection-ttl</link></entry>
<entry>Long</entry>
<entry>the time to live (in ms) for
connections</entry>
- <entry>5 * 60000</entry>
+ <entry>1 * 60000</entry>
</row>
<row>
<entry><link
linkend="flow-control.rate.core.api"
Modified: trunk/docs/user-manual/en/connection-ttl.xml
===================================================================
--- trunk/docs/user-manual/en/connection-ttl.xml 2009-09-28 17:24:07 UTC (rev 8002)
+++ trunk/docs/user-manual/en/connection-ttl.xml 2009-09-28 18:08:09 UTC (rev 8003)
@@ -98,7 +98,7 @@
instance, or if you're deploying JMS connection factory instances direct
into JNDI on
the server side, you can specify it in the xml config, using the parameter
<literal
connection-ttl</literal>.</para>
-
<para>The default value for connection ttl is
<literal>300000</literal>ms, i.e. 5 minutes. A
+ <para>The default value for connection ttl is
<literal>60000</literal>ms, i.e. 1 minute. A
value of <literal>-1</literal> for
<literal>ConnectionTTL</literal> means the server
will never time out the connection on the server side.</para>
<para>If you do not wish clients to be able to specify their own connection
TTL, you can
@@ -151,7 +151,7 @@
deploying JMS connection factory instances direct into JNDI on the server
side, you can
specify it in the <literal>hornetq-jms.xml </literal>
configuration file, using the
parameter
<literal>client-failure-check-period</literal>.</para>
- <para>The default value for client failure check period is
<literal>5000</literal>ms, i.e. 5
+ <para>The default value for client failure check period is
<literal>30000</literal>ms, i.e. 30
seconds. A value of <literal>-1</literal> means the client will
never fail the
connection on the client side if no data is received from the server.
Typically this is
much lower than connection TTL to allow clients to reconnect in case of
transitory