Author: buildbot
Date: Wed Oct 28 12:21:56 2015
New Revision: 970491
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/connection-configuration-uri.html
Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/activemq/content/connection-configuration-uri.html
==============================================================================
--- websites/production/activemq/content/connection-configuration-uri.html
(original)
+++ websites/production/activemq/content/connection-configuration-uri.html Wed
Oct 28 12:21:56 2015
@@ -84,7 +84,7 @@
<div class="wiki-content maincontent"><h2
id="ConnectionConfigurationURI-ConnectionConfigurationURI">Connection
Configuration URI</h2><p>An Apache ActiveMQ connection can be configured by
explicitly setting properties on the <a shape="rect" class="external-link"
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnection.html";>ActiveMQConnection</a>
or <a shape="rect" class="external-link"
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQConnectionFactory.html";>ActiveMQConnectionFactory</a>
objects themselves via the bean properties or using the following URI
syntax.</p><h3 id="ConnectionConfigurationURI-Example">Example</h3><p>You set
the property called jms.$PROPERTY on a regular connection URI. For example you
can set the brokerURL on your ActiveMQConnectionFactory to the following value
to enable <a shape="rect" href="async-sends.html">Async Sends</a></p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeCon
tent panelContent pdl">
<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;">tcp://localhost:61616?jms.useAsyncSend=true
</pre>
-</div></div><h3 id="ConnectionConfigurationURI-ConnectionOptions">Connection
Options</h3><p>The following options should be prefixed with
<strong>jms.</strong> when used on a URI when connecting to a broker.</p><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" class="confluenceTd"><p>alwaysSessionAsync</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>If this flag is set then a separate thread
is used for dispatching messages for each Session in the Connection. However, a
separate thread is always used if there is more than one session, or the
session isn't in auto acknowledge or dups ok mode</p></td></tr><tr><td
colspan="1" rowspan="1" class=
"confluenceTd"><p>clientID</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Sets the JMS clientID to use for the
connection</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>closeTimeout</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>15000ms</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Sets the timeout before a close is considered complete.
Normally a close() on a connection waits for confirmation from the broker; this
allows that operation to timeout to save the client hanging if there is no
broker.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>copyMessageOnSend</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Should a JMS message be copied to a new JMS Message
object as part of the send() method in JMS. This is enabled by default to be
compliant with the JMS spec
ification. You can disable it if you do not mutate JMS messages after they are
sent for a performance boost.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>disableTimeStampsByDefault</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Sets whether or not timestamps on messages should be
disabled or not. If you disable them it adds a small performance
boost.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>dispatchAsync</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Should the broker <a shape="rect"
href="consumer-dispatch-async.html">dispatch messages asynchronously</a> to the
consumer.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>nestedMapAndListEnabled</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1"
class="conflue
nceTd"><p>Enables/disables whether or not <a shape="rect"
href="structured-message-properties-and-mapmessages.html">Structured Message
Properties and MapMessages</a> are supported so that Message properties and
MapMessage entries can contain nested Map and List objects. Available since
version 4.1 onwards</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>objectMessageSerializationDefered</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>When an object is set on an ObjectMessage,
the JMS spec requires the object to be serialized by that set method. Enabling
this flag causes the object to not get serialized. The object may subsequently
get serialized if the message needs to be sent over a socket or stored to
disk.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>optimizeAcknowledge</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>false</p></td><td colspan="1" r
owspan="1" class="confluenceTd"><p>Enables an optimised acknowledgement mode
where messages are acknowledged in batches rather than individually.
Alternatively, you could use Session.DUPS_OK_ACKNOWLEDGE acknowledgement mode
for the consumers which can often be faster. <strong>WARNING</strong> enabling
this issue could cause some issues with auto-acknowledgement on
reconnection</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>optimizeAcknowledgeTimeOut</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>300ms</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>if > 0, specifies the max time between batch acks
when optimizeAcknowledge is enabled. (since 5.6)</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p>optimizedAckScheduledAckInterval</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>if > 0, specifies a <span
style="line-height: 1.4285715;">time int
erval upon which all the outstanding acks are delivered when optimized
acknowledge is used so that a long running consumer that doesn't receive any
more messages will eventually ack the last few unacked messages (since
5.7)</span></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>optimizedMessageDispatch</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>If this flag is set then an larger prefetch limit is
used - only applicable for durable topic subscribers</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>useAsyncSend</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Forces the use of <a shape="rect"
href="async-sends.html">Async Sends</a> which adds a massive performance boost;
but means that the send() method will return immediately whether the message
has been sent or not which could lead to m
essage loss.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>useCompression</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Enables the use of compression of the message
bodies</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>useRetroactiveConsumer</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Sets whether or not retroactive consumers are enabled.
Retroactive consumers allow non-durable topic subscribers to receive old
messages that were published before the non-durable subscriber
started.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>warnAboutUnstartedConnectionTimeout</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>500</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Enables the timeout in milliseconds from a
connection creation to when a w
arning is generated if the connection is not properly started via <a
shape="rect" class="external-link"
href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Connection.html#start()"
rel="nofollow">Connection.start()</a> and a message is received by a consumer.
It is a very common gotcha to forget to <a shape="rect"
href="i-am-not-receiving-any-messages-what-is-wrong.html">start the connection
and then wonder why no messages are delivered</a> so this option makes the
default case to create a warning if the user forgets. To disable the warning
just set the value to < 0 (say -1).</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>auditDepth</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>2048</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>The size of the message window that will be audited
(for duplicates and out of order messages</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>auditMaximumProducerNumber</p></td><td co
lspan="1" rowspan="1" class="confluenceTd"><p>64</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Maximum number of producers that will be
audited</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>alwaysSyncSend</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>When true a MessageProducer will always use Sync sends
when sending a Message even if it is not required for the Delivery
Mode</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>consumerExpiryCheckEnabled</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Controls whether message expiration checking is done in
each MessageConsumer prior to dispatching a message. Disabling this check can
lead to consumption of expired messages. (since
5.11)</p></td></tr></tbody></table></div><h3
id="ConnectionConfigurationURI-NestedOptions">Nested O
ptions</h3><p>You can also configure nested objects on the connection object
using the given prefixes. See the javadoc for a breakdown of each individual
property.</p><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>Object configured</p></th><th colspan="1" rowspan="1"
class="confluenceTh"><p>See Also</p></th></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>jms.blobTransferPolicy.*</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/blob/BlobTransferPolicy.html";>BlobTransferPolicy</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="unresolved" href="#">Blob Message</a></p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>jms.prefetchPolicy.*</p></td><td
colspan="1" rowspa
n="1" class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://http//activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQPrefetchPolicy.html";
rel="nofollow">ActiveMQPrefetchPolicy</a></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect"
href="what-is-the-prefetch-limit-for.html">What is the prefetch limit
for</a></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>jms.redeliveryPolicy.*</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/RedeliveryPolicy.html";>RedeliveryPolicy</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
href="redelivery-policy.html">Redelivery
Policy</a></p></td></tr></tbody></table></div><p>For example you could
set</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><h3 id="ConnectionConfigurationURI-ConnectionOptions">Connection
Options</h3><p>The following options should be prefixed with
<strong>jms.</strong> when used on a URI when connecting to a broker.</p><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" class="confluenceTd"><p>alwaysSessionAsync</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>If this flag is set then a separate thread
is used for dispatching messages for each Session in the Connection. However, a
separate thread is always used if there is more than one session, or the
session isn't in auto acknowledge or dups ok mode</p></td></tr><tr><td
colspan="1" rowspan="1" class=
"confluenceTd"><p>checkForDuplicates</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>If this flag is set to true, the consumer will check
for duplicate messages and properly handle the message to make sure that it is
not processed twice inadvertently.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>clientID</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>null</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Sets the JMS clientID to use for the
connection</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>closeTimeout</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>15000ms</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Sets the timeout before a close is considered complete.
Normally a close() on a connection waits for confirmation from the broker; this
allows that operation to timeout to save the client hanging if there is
no broker.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>copyMessageOnSend</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Should a JMS message be copied to a new JMS Message
object as part of the send() method in JMS. This is enabled by default to be
compliant with the JMS specification. You can disable it if you do not mutate
JMS messages after they are sent for a performance boost.</p></td></tr><tr><td
colspan="1" rowspan="1"
class="confluenceTd"><p>disableTimeStampsByDefault</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Sets whether or not timestamps on messages should be
disabled or not. If you disable them it adds a small performance
boost.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>dispatchAsync</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>false</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Should the broker <a
shape="rect" href="consumer-dispatch-async.html">dispatch messages
asynchronously</a> to the consumer.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>nestedMapAndListEnabled</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Enables/disables whether or not <a
shape="rect"
href="structured-message-properties-and-mapmessages.html">Structured Message
Properties and MapMessages</a> are supported so that Message properties and
MapMessage entries can contain nested Map and List objects. Available since
version 4.1 onwards</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>objectMessageSerializationDefered</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>When an object is set on an ObjectMessage,
the JMS spec requires the object to be
serialized by that set method. Enabling this flag causes the object to not
get serialized. The object may subsequently get serialized if the message needs
to be sent over a socket or stored to disk.</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>optimizeAcknowledge</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Enables an optimised acknowledgement mode where
messages are acknowledged in batches rather than individually. Alternatively,
you could use Session.DUPS_OK_ACKNOWLEDGE acknowledgement mode for the
consumers which can often be faster. <strong>WARNING</strong> enabling this
issue could cause some issues with auto-acknowledgement on
reconnection</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>optimizeAcknowledgeTimeOut</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>300ms</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>if > 0, spec
ifies the max time between batch acks when optimizeAcknowledge is enabled.
(since 5.6)</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>optimizedAckScheduledAckInterval</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>0</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>if > 0, specifies a <span
style="line-height: 1.4285715;">time interval upon which all the outstanding
acks are delivered when optimized acknowledge is used so that a long running
consumer that doesn't receive any more messages will eventually ack the last
few unacked messages (since 5.7)</span></p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>optimizedMessageDispatch</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>true</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>If this flag is set then an larger prefetch
limit is used - only applicable for durable topic
subscribers</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenc
eTd"><p>useAsyncSend</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Forces the use of <a shape="rect"
href="async-sends.html">Async Sends</a> which adds a massive performance boost;
but means that the send() method will return immediately whether the message
has been sent or not which could lead to message loss.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>useCompression</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Enables the use of compression of the
message bodies</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>useRetroactiveConsumer</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Sets whether or not retroactive consumers are enabled.
Retroactive consumers allow non-durable topic subscribers to receive
old messages that were published before the non-durable subscriber
started.</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>warnAboutUnstartedConnectionTimeout</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>500</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Enables the timeout in milliseconds from a
connection creation to when a warning is generated if the connection is not
properly started via <a shape="rect" class="external-link"
href="http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Connection.html#start()"
rel="nofollow">Connection.start()</a> and a message is received by a consumer.
It is a very common gotcha to forget to <a shape="rect"
href="i-am-not-receiving-any-messages-what-is-wrong.html">start the connection
and then wonder why no messages are delivered</a> so this option makes the
default case to create a warning if the user forgets. To disable the warning
just set the value to < 0 (say -1).</p></td></tr><tr><td colspan=
"1" rowspan="1" class="confluenceTd"><p>auditDepth</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>2048</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>The size of the message window that will be audited
(for duplicates and out of order messages</p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>auditMaximumProducerNumber</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>64</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Maximum number of producers that will be
audited</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>alwaysSyncSend</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>false</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>When true a MessageProducer will always use Sync sends
when sending a Message even if it is not required for the Delivery
Mode</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>consumerExpiryCheckEnabled</p></td><td colspan="1" ro
wspan="1" class="confluenceTd"><p>true</p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p>Controls whether message expiration checking is done in
each MessageConsumer prior to dispatching a message. Disabling this check can
lead to consumption of expired messages. (since
5.11)</p></td></tr></tbody></table></div><h3
id="ConnectionConfigurationURI-NestedOptions">Nested Options</h3><p>You can
also configure nested objects on the connection object using the given
prefixes. See the javadoc for a breakdown of each individual property.</p><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>Object configured</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>See Also</p></th></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>jms.blobTransferPolicy.*</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect" cla
ss="external-link"
href="http://activemq.apache.org/maven/apidocs/org/apache/activemq/blob/BlobTransferPolicy.html";>BlobTransferPolicy</a></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="unresolved" href="#">Blob Message</a></p></td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"><p>jms.prefetchPolicy.*</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><a shape="rect"
class="external-link"
href="http://http//activemq.apache.org/maven/apidocs/org/apache/activemq/ActiveMQPrefetchPolicy.html";
rel="nofollow">ActiveMQPrefetchPolicy</a></p></td><td colspan="1" rowspan="1"
class="confluenceTd"><p><a shape="rect"
href="what-is-the-prefetch-limit-for.html">What is the prefetch limit
for</a></p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p>jms.redeliveryPolicy.*</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect" class="external-link"
href="http://activemq.apache.org/maven/apidocs/org/apache/act
ivemq/RedeliveryPolicy.html">RedeliveryPolicy</a></p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p><a shape="rect"
href="redelivery-policy.html">Redelivery
Policy</a></p></td></tr></tbody></table></div><p>For example you could
set</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
<pre class="brush: java; gutter: false; theme: Default"
style="font-size:12px;">tcp://localhost:61616?jms.prefetchPolicy.all=100&jms.redeliveryPolicy.maximumRedeliveries=5
</pre>
</div></div></div>
