Author: buildbot
Date: Wed Mar 27 15:21:44 2013
New Revision: 856177
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/configuring-wire-formats.html
Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/activemq/content/configuring-wire-formats.html
==============================================================================
--- websites/production/activemq/content/configuring-wire-formats.html
(original)
+++ websites/production/activemq/content/configuring-wire-formats.html Wed Mar
27 15:21:44 2013
@@ -76,7 +76,7 @@
<p>OpenWire is the default Wire Format that ActiveMQ uses.  It provides a
highly efficent binary format for high speed messaging.  OpenWire options
can be configured on a JMS client's connection URI string or on a Brokers
transport bind URI.</p>
<div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Parameter Name <br clear="none"
class="atl-forced-newline"> </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value <br clear="none"
class="atl-forced-newline"> </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description <br clear="none" class="atl-forced-newline">
</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
stackTraceEnabled <br clear="none" class="atl-forced-newline"> </td><td
colspan="1" rowspan="1" class="confluenceTd"> true <br clear="none"
class="atl-forced-newline"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Should the stack trace of exception that occur on the
broker be sent to the client? <br clear="none" class="atl-forced-newline">
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
tcpNoDelayEnabled <br clear="none" class="atl-forced-newline"> </td><td
colspan="1" rowspan="1" class="confluenceTd"> false <br cle
ar="none" class="atl-forced-newline"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Does not affect the wire format, but provides a hint to
the peer that TCP nodelay should be enabled on the communications Socket. <br
clear="none" class="atl-forced-newline"> </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> cacheEnabled </td><td colspan="1" rowspan="1"
class="confluenceTd"> true <br clear="none" class="atl-forced-newline">
</td><td colspan="1" rowspan="1" class="confluenceTd"> Should commonly repeated
values be cached so that less marshalling occurs? <br clear="none"
class="atl-forced-newline"> </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> tightEncodingEnabled </td><td colspan="1" rowspan="1"
class="confluenceTd"> true <br clear="none" class="atl-forced-newline">
</td><td colspan="1" rowspan="1" class="confluenceTd"> Should wire size be
optimized over CPU usage ? <br clear="none" class="atl-forced-newline">
</td></tr><tr><td colspan="
1" rowspan="1" class="confluenceTd"> prefixPacketSize  </td><td
colspan="1" rowspan="1" class="confluenceTd"> true <br clear="none"
class="atl-forced-newline"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Should the size of the packet be prefixed before each
packet is marshalled? <br clear="none" class="atl-forced-newline">
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
maxInactivityDuration </td><td colspan="1" rowspan="1" class="confluenceTd">
30000 </td><td colspan="1" rowspan="1" class="confluenceTd"> The maximum <a
shape="rect" href="activemq-inactivitymonitor.html" title="ActiveMQ
InactivityMonitor">inactivity</a> duration (before which the socket is
considered dead) in milliseconds. On some platforms it can take a long time for
a socket to appear to die, so we allow the broker to kill connections if they
are inactive for a period of time. Use by some transports to enable a keep
alive heart beat feature. Set to a value <= 0 to disable
inactivity monitoring. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> maxInactivityDurationInitalDelay </td><td colspan="1"
rowspan="1" class="confluenceTd"> 10000 </td><td colspan="1" rowspan="1"
class="confluenceTd"> The initial delay in starting the maximum <a shape="rect"
href="activemq-inactivitymonitor.html" title="ActiveMQ
InactivityMonitor">inactivity</a> checks (and, yes, the word 'Inital' is
supposed to be misspelled like that) </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> cacheSize </td><td colspan="1" rowspan="1"
class="confluenceTd"> 1024 </td><td colspan="1" rowspan="1"
class="confluenceTd"> If cacheEnabled is true, then this specifies the maximum
number of values to cached. This property was added in ActiveMQ 4.1
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> maxFrameSize
</td><td colspan="1" rowspan="1" class="confluenceTd"> MAX_LONG </td><td
colspan="1" rowspan="1" class="confluenceTd"> Maximum frame size
that can be sent. Can help help prevent OOM DOS attacks
</td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Parameter Name <br clear="none"
class="atl-forced-newline"> </th><th colspan="1" rowspan="1"
class="confluenceTh"> Default Value <br clear="none"
class="atl-forced-newline"> </th><th colspan="1" rowspan="1"
class="confluenceTh"> Description <br clear="none" class="atl-forced-newline">
</th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
stackTraceEnabled <br clear="none" class="atl-forced-newline"> </td><td
colspan="1" rowspan="1" class="confluenceTd"> true <br clear="none"
class="atl-forced-newline"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Should the stack trace of exception that occur on the
broker be sent to the client? <br clear="none" class="atl-forced-newline">
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
tcpNoDelayEnabled <br clear="none" class="atl-forced-newline"> </td><td
colspan="1" rowspan="1" class="confluenceTd"> true <br clea
r="none" class="atl-forced-newline"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Does not affect the wire format, but provides a hint to
the peer that TCP nodelay should be enabled on the communications Socket. <br
clear="none" class="atl-forced-newline"> </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> cacheEnabled </td><td colspan="1" rowspan="1"
class="confluenceTd"> true <br clear="none" class="atl-forced-newline">
</td><td colspan="1" rowspan="1" class="confluenceTd"> Should commonly repeated
values be cached so that less marshalling occurs? <br clear="none"
class="atl-forced-newline"> </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> tightEncodingEnabled </td><td colspan="1" rowspan="1"
class="confluenceTd"> true <br clear="none" class="atl-forced-newline">
</td><td colspan="1" rowspan="1" class="confluenceTd"> Should wire size be
optimized over CPU usage ? <br clear="none" class="atl-forced-newline">
</td></tr><tr><td colspan="1
" rowspan="1" class="confluenceTd"> prefixPacketSize  </td><td
colspan="1" rowspan="1" class="confluenceTd"> true <br clear="none"
class="atl-forced-newline"> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Should the size of the packet be prefixed before each
packet is marshalled? <br clear="none" class="atl-forced-newline">
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
maxInactivityDuration </td><td colspan="1" rowspan="1" class="confluenceTd">
30000 </td><td colspan="1" rowspan="1" class="confluenceTd"> The maximum <a
shape="rect" href="activemq-inactivitymonitor.html" title="ActiveMQ
InactivityMonitor">inactivity</a> duration (before which the socket is
considered dead) in milliseconds. On some platforms it can take a long time for
a socket to appear to die, so we allow the broker to kill connections if they
are inactive for a period of time. Use by some transports to enable a keep
alive heart beat feature. Set to a value <= 0 to disable
inactivity monitoring. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> maxInactivityDurationInitalDelay </td><td colspan="1"
rowspan="1" class="confluenceTd"> 10000 </td><td colspan="1" rowspan="1"
class="confluenceTd"> The initial delay in starting the maximum <a shape="rect"
href="activemq-inactivitymonitor.html" title="ActiveMQ
InactivityMonitor">inactivity</a> checks (and, yes, the word 'Inital' is
supposed to be misspelled like that) </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> cacheSize </td><td colspan="1" rowspan="1"
class="confluenceTd"> 1024 </td><td colspan="1" rowspan="1"
class="confluenceTd"> If cacheEnabled is true, then this specifies the maximum
number of values to cached. This property was added in ActiveMQ 4.1
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> maxFrameSize
</td><td colspan="1" rowspan="1" class="confluenceTd"> MAX_LONG </td><td
colspan="1" rowspan="1" class="confluenceTd"> Maximum frame size
that can be sent. Can help help prevent OOM DOS attacks
</td></tr></tbody></table>
</div>
