You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by bu...@apache.org on 2015/03/06 11:21:56 UTC
svn commit: r942569 - in /websites/production/activemq/content:
activemq-inactivitymonitor.html cache/main.pageCache
tcp-transport-reference.html
Author: buildbot
Date: Fri Mar 6 10:21:55 2015
New Revision: 942569
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/activemq-inactivitymonitor.html
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/tcp-transport-reference.html
Modified: websites/production/activemq/content/activemq-inactivitymonitor.html
==============================================================================
--- websites/production/activemq/content/activemq-inactivitymonitor.html (original)
+++ websites/production/activemq/content/activemq-inactivitymonitor.html Fri Mar 6 10:21:55 2015
@@ -72,19 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h1 id="ActiveMQInactivityMonitor-ActiveMQInactivityMonitor">ActiveMQ InactivityMonitor</h1>
-
-<p>The ActiveMQ InactivityMonitor is an active thread that checks the connection is still active and if it suspects the connection is not functioning correctly, it closes the connection.</p>
-
-<p>Connections are monitored by:</p>
-<ul><li>ensuring data is read from the connection during the specified time period (Max Inactivity Duration)</li><li>writing a KeepAliveInfo message to the connection if no <strong>normal</strong> activemq traffic is sent across the connection during the specified time period</li></ul>
-
-
-<p>Each connection has two InactivityMonitors associated, one on each end of the connection. The InactivityMonitor expects to receive data on the connection during a specified time period. If <strong>normal</strong> activemq traffic has not been sent across the connection during that period, it expects to receive a KeepAliveInfo message sent by the InactivityMonitor on the other end of the connection.</p>
-
-<p>Using the default values; if no data has been read from the connection for 30 seconds, the InactivityMonitor assumes there is an issue with the connection. The InactivityMonitor throws an InactivityIOException and shuts down the transport associated with the connection. This results in the following DEBUG logging:</p>
-
-<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
+<div class="wiki-content maincontent"><h1 id="ActiveMQInactivityMonitor-ActiveMQInactivityMonitor">ActiveMQ InactivityMonitor</h1><p>The ActiveMQ InactivityMonitor is an active thread that checks the connection is still active and if it suspects the connection is not functioning correctly, it closes the connection.</p><p>Connections are monitored by:</p><ul><li>ensuring data is read from the connection during the specified time period (Max Inactivity Duration)</li><li>writing a KeepAliveInfo message to the connection if no <strong>normal</strong> activemq traffic is sent across the connection during the specified time period</li></ul><p>Each connection has two InactivityMonitors associated, one on each end of the connection. The InactivityMonitor expects to receive data on the connection during a specified time period. If <strong>normal</strong> activemq traffic has not been sent across the connection during that period, it expects to receive a KeepAliveInfo message sent by the Inac
tivityMonitor on the other end of the connection.</p><p>Using the default values; if no data has been read from the connection for 30 seconds, the InactivityMonitor assumes there is an issue with the connection. The InactivityMonitor throws an InactivityIOException and shuts down the transport associated with the connection. This results in the following DEBUG logging:</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
<pre>2012-06-26 17:13:55,712 | DEBUG | 30000 ms elapsed since last read check. | org.apache.activemq.transport.AbstractInactivityMonitor
| InactivityMonitor ReadCheck
2012-06-26 17:13:55,712 | DEBUG | No message received since last read check for tcp:///127.0.0.1:52659! Throwing InactivityIOException. |
@@ -99,30 +87,13 @@ org.apache.activemq.transport.Inactivity
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
</pre>
-</div></div>
-
-
-<h3 id="ActiveMQInactivityMonitor-Howtospecifythemaxinactivityduration?">How to specify the max inactivity duration?</h3>
-
-<p>The max inactivity duration can be set by specifying the <strong>wireFormat.maxInactivityDuration</strong> attribute in the connection URL: tcp://localhost:61616?wireFormat.maxInactivityDuration=30000</p>
+</div></div><h3 id="ActiveMQInactivityMonitor-HowcantheInactivityMonitorbeconfiguredfurther?">How can the InactivityMonitor be configured further?</h3><p>There are some configuration options to further fine tune the InactivityMonitor. Note, for most use cases the default values are just fine.</p><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh">Parameter</th><th colspan="1" rowspan="1" class="confluenceTh">Default Value</th><th colspan="1" rowspan="1" class="confluenceTh">Description</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><strong>wireFormat.maxInactivityDuration</strong></td><td colspan="1" rowspan="1" class="confluenceTd">30000 msecs</td><td colspan="1" rowspan="1" class="confluenceTd">Time after with the connection is closed by the broker if no data was received.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><strong>wireFormat.maxInactivityDurationInitalDelay</strong></td><td co
lspan="1" rowspan="1" class="confluenceTd">10000 msecs</td><td colspan="1" rowspan="1" class="confluenceTd">Specifies the maximum delay before inactivity monitoring is started on the connection. It can be useful if a broker is under load with many connections being created concurrently.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><strong>transport.useInactivityMonitor</strong></td><td colspan="1" rowspan="1" class="confluenceTd">true</td><td colspan="1" rowspan="1" class="confluenceTd">A value of false disables the InactivityMonitor completely and connections will never time out. By default it is enabled.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><strong>transport.useKeepAlive</strong></td><td colspan="1" rowspan="1" class="confluenceTd">true</td><td colspan="1" rowspan="1" class="confluenceTd">Whether or not to send a KeepAliveInfo on an idle connection to prevent it from timing out. Enabled by default. Disabling the keep alive will still make
connections time out if no data was received on the connection for the specified amount of time.</td></tr></tbody></table></div><p> </p><p>These parameters can be specified directly on the client side connection URL, e.g. <strong>tcp://localhost:61616?wireFormat.maxInactivityDuration=30000 </strong>or on the broker's transport connector url.</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
+<pre><transportConnectors>
+ <transportConnector name="openwire" uri="tcp://0.0.0.0:61616?wireFormat.maxInactivityDuration=30000&amp;wireFormat.maxInactivityDurationInitalDelay=10000"/>
+</transportConnectors>
-<p>This attribute is valid for both the broker's transport connector URL and the client side connection URL. Default value is 30000 milliseconds.</p>
-
-<h3 id="ActiveMQInactivityMonitor-WhathappensifthemaxInactivityDurationissettodifferentvaluesoneithersideofthesameconnection?">What happens if the maxInactivityDuration is set to different values on either side of the same connection?</h3>
-
-<p>At startup the InactivityMonitor negotiates the appropriate maxInactivityDuration. The shortest duration is taken as the maxInactivityDuration for the connection.</p>
-
-<h3 id="ActiveMQInactivityMonitor-CantheInactivityMonitoronaconnectionbedisabled?">Can the InactivityMonitor on a connection be disabled?</h3>
-
-<p>Setting <strong>wireFormat.maxInactivityDuration=0</strong> will disable the InactivityMonitor</p>
-
-<h3 id="ActiveMQInactivityMonitor-WhatiswireFormat.maxInactivityDurationInitalDelay?">What is wireFormat.maxInactivityDurationInitalDelay?</h3>
-
-<p><strong>wireFormat.maxInactivityDurationInitalDelay</strong> is used to specify the maximum delay before inactivity monitoring is started on the connection. It can be useful if a broker is under load with many connections being created concurrently.<br clear="none" class="atl-forced-newline"></p>
-
-<h3 id="ActiveMQInactivityMonitor-Potentialissuestobeawareof:">Potential issues to be aware of:</h3>
-
-<p><a shape="rect" href="slow-networks-drop-large-messages.html">slow-networks-drop-large-messages</a></p></div>
+</pre>
+</div></div><p> </p><h3 id="ActiveMQInactivityMonitor-WhathappensifthemaxInactivityDurationandmaxInactivityDurationInitalDelayaresettodifferentvaluesoneithersideofthesameconnection?">What happens if the maxInactivityDuration and <strong>maxInactivityDurationInitalDelay</strong> are set to different values on either side of the same connection?</h3><p>At startup the InactivityMonitor negotiates the appropriate maxInactivityDuration and maxInactivityDurationInitalDelay. The shortest duration is taken for the connection.</p><h3 id="ActiveMQInactivityMonitor-CantheInactivityMonitoronaconnectionbedisabled?">Can the InactivityMonitor on a connection be disabled?</h3><p>Setting <strong><strong>transport.useInactivityMonitor</strong>=false </strong>will disable the InactivityMonitor<strong>. </strong>Configuring <strong>wireFormat.maxInactivityDuration=0</strong> will achieve the same result.</p><h3 id="ActiveMQInactivityMonitor-Potentialissuestobeawareof:">Potential issues to be aware
of:</h3><p><a shape="rect" href="slow-networks-drop-large-messages.html">slow-networks-drop-large-messages</a></p></div>
</td>
<td valign="top">
<div class="navigation">
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 Fri Mar 6 10:21:55 2015
@@ -72,7 +72,7 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h3 id="TCPTransportReference-TheTCPTransport">The TCP Transport</h3><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 id="TCPTransportReference-ConfigurationSyntax">Configuration Syntax</h4><p><strong>tcp://hostname:port?key=value</strong></p><h5 id="TCPTransportReference-TransportOptions">Transport Options</h5><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" cla
ss="confluenceTd"><p>minmumWireFormatVersion</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The minimum version wireformat that is allowed</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>trace</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Causes all commands that are sent over the transport to be logged (to view use config of the form: log4j.logger.org.apache.activemq.transport.TransportLogger=DEBUG)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>daemon</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Tells the transport thread to run as a daemon or not. Useful to enable when embedding in a Spring container or a web container to allow the container to shut down properly.</p></td></tr><tr><td colspan="1" rowspan="
1" class="confluenceTd"><p>useLocalHost</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When true, it causes the local machines name to resolve to "localhost".</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>socketBufferSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>64 * 1024</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the socket buffer size in bytes</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>keepAlive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When true, enables <a shape="rect" class="external-link" href="http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html" rel="nofollow">TCP KeepAlive</a> on the broker connection. Ensures connections don't time out on TCP level. Not used by InactivityMonitor!</p></td></tr><tr><td colspan="1" rowspan="
1" class="confluenceTd"><p>soTimeout</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>sets the socket timeout in milliseconds</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connectionTimeout</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>30000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A non-zero value specifies the connection timeout in milliseconds. A zero value means wait forever for the connection to be established. Negative values are ignored.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>default</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the WireFormat to use</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rows
pan="1" class="confluenceTd"><p>All the properties with this prefix are used to configure the wireFormat. See <a shape="rect" href="configuring-wire-formats.html">Configuring Wire Formats</a> for more information</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>closeAsync</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The false value causes all sockets to be closed synchronously</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>soLinger</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>MIN_INTEGER</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When > -1 causes the socket soLinger option to be enabled with this value. When == -1, causes soLinger to be disabled. (from 5.6.0)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maximumConnections</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Integer.MAX_VALUE</p></t
d><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of sockets the broker is allowed to create</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>diffServ</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>client only) The preferred Differentiated Services traffic class to be set on outgoing packets, as described in RFC 2475. Valid integer values: [0,64). Valid string values: EF, AF[1-3][1-4] or CS[0-7]. With JDK 6, only works when the Java Runtime uses the IPv4 stack, which can be done by setting the java.net.preferIPv4Stack system property to be true. Cannot be used at the same time as the typeOfService option.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>typeOfService</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(client only) The preferred Type of Service value to be set o
n outgoing packets. Valid integer values: [0,256). With JDK 6, only works when the Java Runtime uses the IPv4 stack, which can be done by setting the java.net.preferIPv4Stack system property to be true. Cannot be used at the same time as the diffServ option</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>tcpNoDelay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When true, the TCP_NODELAY setting is enabled on the socket.</p></td></tr></tbody></table></div><h5 id="TCPTransportReference-ExampleURI">Example URI</h5><p>On Server side (in TransportConnector)</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">
+<div class="wiki-content maincontent"><h3 id="TCPTransportReference-TheTCPTransport">The TCP Transport</h3><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 id="TCPTransportReference-ConfigurationSyntax">Configuration Syntax</h4><p><strong>tcp://hostname:port?key=value</strong></p><h5 id="TCPTransportReference-TransportOptions">Transport Options</h5><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option Name</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" cla
ss="confluenceTd"><p>minmumWireFormatVersion</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The minimum version wireformat that is allowed</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>trace</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Causes all commands that are sent over the transport to be logged (to view use config of the form: log4j.logger.org.apache.activemq.transport.TransportLogger=DEBUG)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>daemon</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Tells the transport thread to run as a daemon or not. Useful to enable when embedding in a Spring container or a web container to allow the container to shut down properly.</p></td></tr><tr><td colspan="1" rowspan="
1" class="confluenceTd"><p>useLocalHost</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When true, it causes the local machines name to resolve to "localhost".</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>socketBufferSize</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>64 * 1024</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Sets the socket buffer size in bytes</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>keepAlive</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When true, enables <a shape="rect" class="external-link" href="http://tldp.org/HOWTO/TCP-Keepalive-HOWTO/overview.html" rel="nofollow">TCP KeepAlive</a> on the broker connection. Ensures connections don't time out on TCP level. Not used by InactivityMonitor!</p></td></tr><tr><td colspan="1" rowspan="
1" class="confluenceTd">useKeepAlive</td><td colspan="1" rowspan="1" class="confluenceTd">true</td><td colspan="1" rowspan="1" class="confluenceTd">Whether or not the <a shape="rect" href="activemq-inactivitymonitor.html">InactivitiyMonitor</a> should send KeepAliveInfo messages on idle connections. Enabled by default.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>soTimeout</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>sets the socket timeout in milliseconds</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>connectionTimeout</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>30000</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A non-zero value specifies the connection timeout in milliseconds. A zero value means wait forever for the connection to be established. Negative values are ignored.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluen
ceTd"><p>wireFormat</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>default</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The name of the WireFormat to use</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.*</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p> </p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>All the properties with this prefix are used to configure the wireFormat. See <a shape="rect" href="configuring-wire-formats.html">Configuring Wire Formats</a> for more information</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>closeAsync</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The false value causes all sockets to be closed synchronously</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>soLinger</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>MIN_INTEGER</p></td>
<td colspan="1" rowspan="1" class="confluenceTd"><p>When > -1 causes the socket soLinger option to be enabled with this value. When == -1, causes soLinger to be disabled. (from 5.6.0)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>maximumConnections</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Integer.MAX_VALUE</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum number of sockets the broker is allowed to create</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>diffServ</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>client only) The preferred Differentiated Services traffic class to be set on outgoing packets, as described in RFC 2475. Valid integer values: [0,64). Valid string values: EF, AF[1-3][1-4] or CS[0-7]. With JDK 6, only works when the Java Runtime uses the IPv4 stack, which can be done by setting the java.net.preferIPv4St
ack system property to be true. Cannot be used at the same time as the typeOfService option.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>typeOfService</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>(client only) The preferred Type of Service value to be set on outgoing packets. Valid integer values: [0,256). With JDK 6, only works when the Java Runtime uses the IPv4 stack, which can be done by setting the java.net.preferIPv4Stack system property to be true. Cannot be used at the same time as the diffServ option</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p>tcpNoDelay</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>When true, the TCP_NODELAY setting is enabled on the socket.</p></td></tr></tbody></table></div><h5 id="TCPTransportReference-ExampleURI">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&transport.soTimeout=60000
</pre>
</div></div><p>On Client side</p><div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent">