Author: buildbot
Date: Fri Oct 14 17:22:34 2016
New Revision: 999437

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/activemq-inactivitymonitor.html
    websites/production/activemq/content/cache/main.pageCache

Modified: websites/production/activemq/content/activemq-inactivitymonitor.html
==============================================================================
--- websites/production/activemq/content/activemq-inactivitymonitor.html 
(original)
+++ websites/production/activemq/content/activemq-inactivitymonitor.html Fri 
Oct 14 17:22:34 2016
@@ -70,7 +70,7 @@
 <p></p>
         <div class="top_red_bar">
           <div id="site-breadcrumbs">
-<a href="using-activemq-4.html">Using ActiveMQ 4</a>&nbsp;&gt;&nbsp;<a 
href="configuring-transports.html">Configuring Transports</a>&nbsp;&gt;&nbsp;<a 
href="activemq-inactivitymonitor.html">ActiveMQ InactivityMonitor</a>
+<a href="using-activemq.html">Using ActiveMQ</a>&nbsp;&gt;&nbsp;<a 
href="configuring-transports.html">Configuring Transports</a>&nbsp;&gt;&nbsp;<a 
href="activemq-inactivitymonitor.html">ActiveMQ InactivityMonitor</a>
           </div>
           <div id="site-quicklinks">
 <p><a shape="rect" href="download.html">Download</a> | <a shape="rect" 
class="external-link" 
href="http://activemq.apache.org/maven/apidocs/index.html";>JavaDocs</a> <a 
shape="rect" href="javadocs.html">More...</a> | <a shape="rect" 
href="source.html">Source</a> | <a shape="rect" 
href="discussion-forums.html">Forums</a> | <a shape="rect" 
href="support.html">Support</a></p>
@@ -81,7 +81,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&#160;<strong><code>KeepAliveInfo</code></strong> 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&#16
 0;<strong><code>KeepAliveInfo</code></strong> message sent by the 
InactivityMonitor on the other end of the connection.</p><p>Using the default 
values; if no data has been written or read from the connection for 30 seconds, 
the InactivityMonitor kicks in. The InactivityMonitor throws 
an&#160;<strong><code>InactivityIOException</code></strong> and shuts down the 
transport associated with the connection. This results in the 
following&#160;<strong><code>DEBUG</code></strong> 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&#160;<strong><code>KeepAliveInfo</code></strong> 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&#
 160;<strong><code>KeepAliveInfo</code></strong> message sent by the 
InactivityMonitor on the other end of the connection.</p><p>Using the default 
values; if no data has been written or read from the connection for 30 seconds, 
the InactivityMonitor kicks in. The InactivityMonitor throws 
an&#160;<strong><code>InactivityIOException</code></strong> and shuts down the 
transport associated with the connection. This results in the 
following&#160;<strong><code>DEBUG</code></strong> 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. | 
org.apache.activemq.transport.AbstractInactivityMonitor | InactivityMonitor 
ReadCheck
 2012-06-26 17:13:55,714 | DEBUG | Transport Connection to: 
tcp://127.0.0.1:52659 failed: 
@@ -94,12 +94,12 @@ 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-AdvancedInactivityMonitorConfiguration">Advanced 
InactivityMonitor Configuration</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"><code>wireFormat.maxInactivityDuration</code></td><td 
colspan="1" rowspan="1" class="confluenceTd"><code>30000</code></td><td 
colspan="1" rowspan="1" class="confluenceTd">The time, in milliseconds, after 
which the connection is closed by the broker if no data has been 
received.</td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><code>wireFormat.maxInactivityDurationInitalDelay</code></td
 ><td colspan="1" rowspan="1" class="confluenceTd"><code>10000</code></td><td 
 >colspan="1" rowspan="1" class="confluenceTd"><p>Specifies the maximum delay, 
 >in milliseconds, before connection inactivity monitoring is 
 >started.</p><p>This can prove useful if a broker is under load with many 
 >connections being created concurrently.</p></td></tr><tr><td colspan="1" 
 >rowspan="1" 
 >class="confluenceTd"><code>transport.useInactivityMonitor</code></td><td 
 >colspan="1" rowspan="1" class="confluenceTd"><code>true</code></td><td 
 >colspan="1" rowspan="1" class="confluenceTd"><p>A value 
 >of&#160;<strong><code>false</code></strong> disables the InactivityMonitor 
 >completely and connections will never time out.</p><p>By default it is 
 >enabled.</p></td></tr><tr><td colspan="1" rowspan="1" 
 >class="confluenceTd"><code>transport.useKeepAlive</code></td><td colspan="1" 
 >rowspan="1" class="confluenceTd"><code>true</code></td><td colspan="1" 
 >rowspan="1" class="confluenceTd"><p>Determines if a&#160;<strong><code>KeepAl
 iveInfo</code></strong> message should be sent on an idle connection to 
prevent it from timing out.</p><p>Disabling the keep alive will still make 
connections time out when no data was received on the connection for the 
specified amount of time.</p><p>Enabled by 
default.</p></td></tr></tbody></table></div><p>&#160;</p><p>These parameters 
can be specified directly on the client side connection URL, e.g. 
<strong><code>tcp://localhost:61616?wireFormat.maxInactivityDuration=30000</code>,
 </strong>or on the broker's transport connector URL:</p><div class="code panel 
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 
id="ActiveMQInactivityMonitor-AdvancedInactivityMonitorConfiguration">Advanced 
InactivityMonitor Configuration</h3><p>There are some configuration options to 
further fine tune the <code>InactivityMonitor</code>. 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"><p><code>wireFormat.maxInactivityDuration</code></p></td><td
 colspan="1" rowspan="1" class="confluenceTd"><p><code>30000</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>Timeout, in milliseconds, after 
which the connection is closed by the broker if no data has been 
received.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>wireFormat.maxInac
 tivityDurationInitalDelay</code></p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>10000</code></p></td><td colspan="1" rowspan="1" 
class="confluenceTd"><p>Specifies the maximum delay, in milliseconds, before 
connection inactivity monitoring is started.</p><p>This can prove useful if a 
broker is under load with many connections being created 
concurrently.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>transport.useInactivityMonitor</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p>A value 
of&#160;<strong><code>false</code></strong> disables 
the&#160;<code>InactivityMonitor</code> completely and connections will never 
time out.</p></td></tr><tr><td colspan="1" rowspan="1" 
class="confluenceTd"><p><code>transport.useKeepAlive</code></p></td><td 
colspan="1" rowspan="1" class="confluenceTd"><p><code>true</code></p></td><td 
colspan="1" rowspan="1" clas
 s="confluenceTd"><p>Determines if 
a&#160;<strong><code>KeepAliveInfo</code></strong> message should be sent on an 
idle connection to prevent it from timing out.</p><p>Disabling the keep alive 
will still make connections time out when no data was received on the 
connection for the specified amount of 
time.</p></td></tr></tbody></table></div><p>&#160;</p><p>These parameters can 
be specified directly on the client side connection URL, e.g. 
<strong><code>tcp://localhost:61616?wireFormat.maxInactivityDuration=30000</code>,
 </strong>or on the broker's transport connector URL:</p><div class="code panel 
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <pre class="brush: xml; gutter: false; theme: Default" 
style="font-size:12px;">&lt;transportConnectors&gt;
   &lt;transportConnector name="openwire" 
uri="tcp://0.0.0.0:61616?wireFormat.maxInactivityDuration=30000&amp;amp;wireFormat.maxInactivityDurationInitalDelay=10000"/&gt;
 &lt;/transportConnectors&gt;
 </pre>
-</div></div><h3 
id="ActiveMQInactivityMonitor-WhathappensifthemaxInactivityDurationandmaxInactivityDurationInitalDelayaresettodifferentvaluesoneithersideofthesameconnection?">What
 happens if the&#160;<code>maxInactivityDuration</code> and 
<code>maxInactivityDurationInitalDelay</code> are set to different values on 
either side of the same connection?</h3><p>At startup the InactivityMonitor 
negotiates the 
appropriate&#160;<strong><code>maxInactivityDuration</code></strong> 
and&#160;<strong><code>maxInactivityDurationInitalDelay</code></strong>. 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><code>transport.useInactivityMonitor=false</code></strong> will disable 
the InactivityMonitor<strong>. </strong>Configuring 
<strong><code>wireFormat.maxInactivityDuration=0</code></strong> will achieve 
the same result.</p><h3 id="Act
 iveMQInactivityMonitor-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><p>&#160;</p></div>
+</div></div><h3 
id="ActiveMQInactivityMonitor-WhathappensifthemaxInactivityDurationandmaxInactivityDurationInitalDelayaresettodifferentvaluesoneithersideofthesameconnection?">What
 happens if the&#160;<code>maxInactivityDuration</code> and 
<code>maxInactivityDurationInitalDelay</code> are set to different values on 
either side of the same connection?</h3><p>At startup the InactivityMonitor 
negotiates the 
appropriate&#160;<strong><code>maxInactivityDuration</code></strong> 
and&#160;<strong><code>maxInactivityDurationInitalDelay</code></strong>. 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><code>transport.useInactivityMonitor=false</code></strong> will disable 
the InactivityMonitor<strong>. </strong>Configuring 
<strong><code>wireFormat.maxInactivityDuration=0</code></strong> will achieve 
the same result.</p><h3 id="Act
 iveMQInactivityMonitor-PotentialIssues">Potential Issues</h3><p><a 
shape="rect" 
href="slow-networks-drop-large-messages.html">slow-networks-drop-large-messages</a></p><p>&#160;</p></div>
         </td>
         <td valign="top">
           <div class="navigation">

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


Reply via email to