svn commit: r861908 - in /websites/production/activemq/content: cache/main.pageCache tcp-transport-reference.html

[bu...@apache.org]

Author: buildbot
Date: Tue May 14 02:21:42 2013
New Revision: 861908

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/tcp-transport-reference.html

Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/activemq/content/tcp-transport-reference.html
==============================================================================
--- websites/production/activemq/content/tcp-transport-reference.html (original)
+++ websites/production/activemq/content/tcp-transport-reference.html Tue May 14 02:21:42 2013
@@ -76,6 +76,10 @@
 
 <p>The TCP transport allows clients to connect to a remote ActiveMQ broker using a TCP socket.</p>
 
+<p>These configuration options are used to tune the underlying TCP transport, and can be configured on a JMS client's connection URI string or on a Brokers transport bind URI.</p>
+
+<p>The options below should be prefixed with transport.* when used on the server side.</p>
+
 <h4><a shape="rect" name="TCPTransportReference-ConfigurationSyntax"></a>Configuration Syntax</h4>
 
 <p><b>tcp://hostname:port?key=value</b></p>
@@ -89,6 +93,13 @@
 
 <h5><a shape="rect" name="TCPTransportReference-ExampleURI"></a>Example URI</h5>
 
+<p>On Server side (in TransportConnector)</p>
+<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
+<pre>tcp://localhost:61616?transport.trace=false&amp;transport.soTimeout=60000
+</pre>
+</div></div>
+
+<p>On Client side</p>
 <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
 <pre>tcp://localhost:61616?trace=false&amp;soTimeout=60000
 </pre>