Author: buildbot
Date: Thu Nov 22 13:22:12 2012
New Revision: 839144
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-component-appendix.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/jms.html
Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Thu Nov 22
13:22:12 2012
@@ -8958,7 +8958,7 @@ In Camel 2.8 onwards, the default settin
<h4><a shape="rect"
name="BookComponentAppendix-Mostcommonlyusedoptions"></a>Most commonly used
options</h4>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </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"> <tt>clientId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets the JMS client ID to use. Note that this value, if
specified, must be unique and can only be used by a single JMS connection
instance. It is typically only required for durable topic subscriptions. You
may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class
="confluenceTd"> Specifies the default number of concurrent consumers. From
<b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>disableReplyTo</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If <tt>true</tt>, a producer will behave like a InOnly
exchange with the exception that <tt>JMSReplyTo</tt> header is sent out and not
be suppressed like in the case of <tt>InOnly</tt>. Like <tt>InOnly</tt> the
producer will not wait for a reply. A consumer with this flag will behave like
<tt>InOnly</tt>. This feature can be used to bridge <tt>InOut</tt> requests to
another queue so that a route on the other queue will send it´s response
directly back to the original <tt>JMSReplyTo</tt>. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>durableSubscriptionName</tt>
</td><td cols
pan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> The durable subscriber name for specifying
durable topic subscriptions. The <tt>clientId</tt> option <b>must</b> be
configured as well. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>maxConcurrentConsumers</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Specifies the maximum number of concurrent consumers.
From <b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>maxMessagesPerTask</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The number of messages per task. -1 is unlimited. If you
use a range for concurrent consumers (eg min < max), then this option can be
used to set a value to
eg <tt>100</tt> to control how fast the consumers will shrink when less work
is required. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>preserveMessageQos</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Set to <tt>true</tt>, if you want to send message using
the QoS settings specified on the message, instead of the QoS settings on the
JMS endpoint. The following three headers are considered <tt>JMSPriority</tt>,
<tt>JMSDeliveryMode</tt>, and <tt>JMSExpiration</tt>. You can provide all or
only some of them. If not provided, Camel will fall back to use the values from
the endpoint instead. So, when using this option, the headers override the
values from the endpoint. The <tt>explicitQosEnabled</tt> option, by contrast,
will only use options set on the endpoint, and not values from the message
header. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>replyTo
</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> Provides an explicit
ReplyTo destination, which overrides any incoming value of
<tt>Message.getJMSReplyTo()</tt>. If you do <a shape="rect"
href="request-reply.html" title="Request Reply">Request Reply</a> over JMS then
<b>make sure</b> to read the section <em>Request-reply over JMS</em> further
below for more details, and the <tt>replyToType</tt> option as well.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>replyToType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel
2.9:</b> Allows for explicitly specifying which kind of strategy to use for
replyTo queues when doing request/reply over JMS. Possible values are:
<tt>Temporary</tt>, <tt>Shared</tt>, or <tt>Exclusive</tt>. By default Camel
will use temporary queues. However if <tt>replyTo</
tt> has been configured, then <tt>Shared</tt> is used by default. This option
allows you to use exclusive queues instead of shared ones. See further below
for more details, and especially the notes about the implications if running in
a clustered environment, and the fact that <tt>Shared</tt> reply queues has
lower performance than its alternatives <tt>Temporary</tt> and
<tt>Exclusive</tt>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>requestTimeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>20000</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Producer only:</b> The timeout for waiting for a reply
when using the InOut <a shape="rect" href="exchange-pattern.html"
title="Exchange Pattern">Exchange Pattern</a> (in milliseconds). The default is
20 seconds. See below in section <em>About time to live</em> for more details.
See also the <em>requestTimeoutCheckerInterval</em> option. </td></tr><tr><td
colspan="1" rowspan="
1" class="confluenceTd"> <tt>selector</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets the JMS Selector, which is an SQL 92 predicate that
is used to filter messages within the broker. You may have to encode special
characters such as = as %3D <b>Before Camel 2.3.0</b>, we don't support this
option in CamelConsumerTemplate </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeToLive</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When sending messages, specifies the time-to-live of the
message (in milliseconds). See below in section <em>About time to live</em> for
more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>transacted</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies
w
hether to use transacted mode for sending/receiving messages using the InOnly
<a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange
Pattern</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>testConnectionOnStartup</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.1:</b> Specifies whether to test the
connection on startup. This ensures that when Camel starts that all the JMS
consumers have a valid connection to the JMS broker. If a connection cannot be
granted then Camel throws an exception on startup. This ensures that Camel is
not started with failed connections. From <b>Camel 2.8</b> onwards also the JMS
producers is tested as well. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </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"> <tt>clientId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets the JMS client ID to use. Note that this value, if
specified, must be unique and can only be used by a single JMS connection
instance. It is typically only required for durable topic subscriptions. You
may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class
="confluenceTd"> Specifies the default number of concurrent consumers. From
<b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. See also the <tt>maxMessagesPerTask</tt> option to
control dynamic scaling up/down of threads. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>disableReplyTo</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> If <tt>true</tt>, a producer will behave like
a InOnly exchange with the exception that <tt>JMSReplyTo</tt> header is sent
out and not be suppressed like in the case of <tt>InOnly</tt>. Like
<tt>InOnly</tt> the producer will not wait for a reply. A consumer with this
flag will behave like <tt>InOnly</tt>. This feature can be used to bridge
<tt>InOut</tt> requests to another queue so that a route on the other queue
will send it´s response directly back to the original <tt>JMSReplyTo</tt>.
</td></tr><tr><
td colspan="1" rowspan="1" class="confluenceTd">
<tt>durableSubscriptionName</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The durable subscriber name for specifying durable topic
subscriptions. The <tt>clientId</tt> option <b>must</b> be configured as well.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>maxConcurrentConsumers</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Specifies the maximum number of concurrent consumers.
From <b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. See also the <tt>maxMessagesPerTask</tt> option to
control dynamic scaling up/down of threads. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>maxMessagesPerTask</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1"
rows
pan="1" class="confluenceTd"> The number of messages per task. -1 is
unlimited. If you use a range for concurrent consumers (eg min < max), then
this option can be used to set a value to eg <tt>100</tt> to control how fast
the consumers will shrink when less work is required. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>preserveMessageQos</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Set to <tt>true</tt>, if you want
to send message using the QoS settings specified on the message, instead of the
QoS settings on the JMS endpoint. The following three headers are considered
<tt>JMSPriority</tt>, <tt>JMSDeliveryMode</tt>, and <tt>JMSExpiration</tt>. You
can provide all or only some of them. If not provided, Camel will fall back to
use the values from the endpoint instead. So, when using this option, the
headers override the values from the endpoint. The <tt>explicitQosEn
abled</tt> option, by contrast, will only use options set on the endpoint, and
not values from the message header. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>replyTo</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Provides an explicit ReplyTo destination, which overrides
any incoming value of <tt>Message.getJMSReplyTo()</tt>. If you do <a
shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a>
over JMS then <b>make sure</b> to read the section <em>Request-reply over
JMS</em> further below for more details, and the <tt>replyToType</tt> option as
well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>replyToType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel
2.9:</b> Allows for explicitly specifying which kind of strategy to use for
replyTo q
ueues when doing request/reply over JMS. Possible values are:
<tt>Temporary</tt>, <tt>Shared</tt>, or <tt>Exclusive</tt>. By default Camel
will use temporary queues. However if <tt>replyTo</tt> has been configured,
then <tt>Shared</tt> is used by default. This option allows you to use
exclusive queues instead of shared ones. See further below for more details,
and especially the notes about the implications if running in a clustered
environment, and the fact that <tt>Shared</tt> reply queues has lower
performance than its alternatives <tt>Temporary</tt> and <tt>Exclusive</tt>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>requestTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>20000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<b>Producer only:</b> The timeout for waiting for a reply when using the InOut
<a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange
Pattern</a> (in milliseconds). The
default is 20 seconds. See below in section <em>About time to live</em> for
more details. See also the <em>requestTimeoutCheckerInterval</em> option.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>selector</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sets the
JMS Selector, which is an SQL 92 predicate that is used to filter messages
within the broker. You may have to encode special characters such as = as %3D
<b>Before Camel 2.3.0</b>, we don't support this option in
CamelConsumerTemplate </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeToLive</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When sending messages, specifies the time-to-live of the
message (in milliseconds). See below in section <em>About time to live</em> for
more details. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>transacted</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Specifies whether to use transacted mode for
sending/receiving messages using the InOnly <a shape="rect"
href="exchange-pattern.html" title="Exchange Pattern">Exchange Pattern</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>testConnectionOnStartup</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.1:</b> Specifies whether to test the
connection on startup. This ensures that when Camel starts that all the JMS
consumers have a valid connection to the JMS broker. If a connection cannot be
granted then Camel throws an exception on startup. This ensures that Camel is
not started with failed connections. From <b>Camel 2.8</b> onwards also the JMS
producers is tested as well. </td></tr></tbody
></table>
</div>
Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Thu Nov 22 13:22:12
2012
@@ -29194,7 +29194,7 @@ In Camel 2.8 onwards, the default settin
<h4><a shape="rect" name="BookInOnePage-Mostcommonlyusedoptions"></a>Most
commonly used options</h4>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </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"> <tt>clientId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets the JMS client ID to use. Note that this value, if
specified, must be unique and can only be used by a single JMS connection
instance. It is typically only required for durable topic subscriptions. You
may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class
="confluenceTd"> Specifies the default number of concurrent consumers. From
<b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>disableReplyTo</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If <tt>true</tt>, a producer will behave like a InOnly
exchange with the exception that <tt>JMSReplyTo</tt> header is sent out and not
be suppressed like in the case of <tt>InOnly</tt>. Like <tt>InOnly</tt> the
producer will not wait for a reply. A consumer with this flag will behave like
<tt>InOnly</tt>. This feature can be used to bridge <tt>InOut</tt> requests to
another queue so that a route on the other queue will send it´s response
directly back to the original <tt>JMSReplyTo</tt>. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>durableSubscriptionName</tt>
</td><td cols
pan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> The durable subscriber name for specifying
durable topic subscriptions. The <tt>clientId</tt> option <b>must</b> be
configured as well. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>maxConcurrentConsumers</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Specifies the maximum number of concurrent consumers.
From <b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>maxMessagesPerTask</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The number of messages per task. -1 is unlimited. If you
use a range for concurrent consumers (eg min < max), then this option can be
used to set a value to
eg <tt>100</tt> to control how fast the consumers will shrink when less work
is required. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>preserveMessageQos</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Set to <tt>true</tt>, if you want to send message using
the QoS settings specified on the message, instead of the QoS settings on the
JMS endpoint. The following three headers are considered <tt>JMSPriority</tt>,
<tt>JMSDeliveryMode</tt>, and <tt>JMSExpiration</tt>. You can provide all or
only some of them. If not provided, Camel will fall back to use the values from
the endpoint instead. So, when using this option, the headers override the
values from the endpoint. The <tt>explicitQosEnabled</tt> option, by contrast,
will only use options set on the endpoint, and not values from the message
header. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>replyTo
</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> Provides an explicit
ReplyTo destination, which overrides any incoming value of
<tt>Message.getJMSReplyTo()</tt>. If you do <a shape="rect"
href="request-reply.html" title="Request Reply">Request Reply</a> over JMS then
<b>make sure</b> to read the section <em>Request-reply over JMS</em> further
below for more details, and the <tt>replyToType</tt> option as well.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>replyToType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel
2.9:</b> Allows for explicitly specifying which kind of strategy to use for
replyTo queues when doing request/reply over JMS. Possible values are:
<tt>Temporary</tt>, <tt>Shared</tt>, or <tt>Exclusive</tt>. By default Camel
will use temporary queues. However if <tt>replyTo</
tt> has been configured, then <tt>Shared</tt> is used by default. This option
allows you to use exclusive queues instead of shared ones. See further below
for more details, and especially the notes about the implications if running in
a clustered environment, and the fact that <tt>Shared</tt> reply queues has
lower performance than its alternatives <tt>Temporary</tt> and
<tt>Exclusive</tt>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>requestTimeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>20000</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Producer only:</b> The timeout for waiting for a reply
when using the InOut <a shape="rect" href="exchange-pattern.html"
title="Exchange Pattern">Exchange Pattern</a> (in milliseconds). The default is
20 seconds. See below in section <em>About time to live</em> for more details.
See also the <em>requestTimeoutCheckerInterval</em> option. </td></tr><tr><td
colspan="1" rowspan="
1" class="confluenceTd"> <tt>selector</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets the JMS Selector, which is an SQL 92 predicate that
is used to filter messages within the broker. You may have to encode special
characters such as = as %3D <b>Before Camel 2.3.0</b>, we don't support this
option in CamelConsumerTemplate </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeToLive</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When sending messages, specifies the time-to-live of the
message (in milliseconds). See below in section <em>About time to live</em> for
more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>transacted</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies
w
hether to use transacted mode for sending/receiving messages using the InOnly
<a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange
Pattern</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>testConnectionOnStartup</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.1:</b> Specifies whether to test the
connection on startup. This ensures that when Camel starts that all the JMS
consumers have a valid connection to the JMS broker. If a connection cannot be
granted then Camel throws an exception on startup. This ensures that Camel is
not started with failed connections. From <b>Camel 2.8</b> onwards also the JMS
producers is tested as well. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </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"> <tt>clientId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets the JMS client ID to use. Note that this value, if
specified, must be unique and can only be used by a single JMS connection
instance. It is typically only required for durable topic subscriptions. You
may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class
="confluenceTd"> Specifies the default number of concurrent consumers. From
<b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. See also the <tt>maxMessagesPerTask</tt> option to
control dynamic scaling up/down of threads. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>disableReplyTo</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> If <tt>true</tt>, a producer will behave like
a InOnly exchange with the exception that <tt>JMSReplyTo</tt> header is sent
out and not be suppressed like in the case of <tt>InOnly</tt>. Like
<tt>InOnly</tt> the producer will not wait for a reply. A consumer with this
flag will behave like <tt>InOnly</tt>. This feature can be used to bridge
<tt>InOut</tt> requests to another queue so that a route on the other queue
will send it´s response directly back to the original <tt>JMSReplyTo</tt>.
</td></tr><tr><
td colspan="1" rowspan="1" class="confluenceTd">
<tt>durableSubscriptionName</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The durable subscriber name for specifying durable topic
subscriptions. The <tt>clientId</tt> option <b>must</b> be configured as well.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>maxConcurrentConsumers</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Specifies the maximum number of concurrent consumers.
From <b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. See also the <tt>maxMessagesPerTask</tt> option to
control dynamic scaling up/down of threads. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>maxMessagesPerTask</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1"
rows
pan="1" class="confluenceTd"> The number of messages per task. -1 is
unlimited. If you use a range for concurrent consumers (eg min < max), then
this option can be used to set a value to eg <tt>100</tt> to control how fast
the consumers will shrink when less work is required. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>preserveMessageQos</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Set to <tt>true</tt>, if you want
to send message using the QoS settings specified on the message, instead of the
QoS settings on the JMS endpoint. The following three headers are considered
<tt>JMSPriority</tt>, <tt>JMSDeliveryMode</tt>, and <tt>JMSExpiration</tt>. You
can provide all or only some of them. If not provided, Camel will fall back to
use the values from the endpoint instead. So, when using this option, the
headers override the values from the endpoint. The <tt>explicitQosEn
abled</tt> option, by contrast, will only use options set on the endpoint, and
not values from the message header. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>replyTo</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Provides an explicit ReplyTo destination, which overrides
any incoming value of <tt>Message.getJMSReplyTo()</tt>. If you do <a
shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a>
over JMS then <b>make sure</b> to read the section <em>Request-reply over
JMS</em> further below for more details, and the <tt>replyToType</tt> option as
well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>replyToType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel
2.9:</b> Allows for explicitly specifying which kind of strategy to use for
replyTo q
ueues when doing request/reply over JMS. Possible values are:
<tt>Temporary</tt>, <tt>Shared</tt>, or <tt>Exclusive</tt>. By default Camel
will use temporary queues. However if <tt>replyTo</tt> has been configured,
then <tt>Shared</tt> is used by default. This option allows you to use
exclusive queues instead of shared ones. See further below for more details,
and especially the notes about the implications if running in a clustered
environment, and the fact that <tt>Shared</tt> reply queues has lower
performance than its alternatives <tt>Temporary</tt> and <tt>Exclusive</tt>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>requestTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>20000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<b>Producer only:</b> The timeout for waiting for a reply when using the InOut
<a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange
Pattern</a> (in milliseconds). The
default is 20 seconds. See below in section <em>About time to live</em> for
more details. See also the <em>requestTimeoutCheckerInterval</em> option.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>selector</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sets the
JMS Selector, which is an SQL 92 predicate that is used to filter messages
within the broker. You may have to encode special characters such as = as %3D
<b>Before Camel 2.3.0</b>, we don't support this option in
CamelConsumerTemplate </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeToLive</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When sending messages, specifies the time-to-live of the
message (in milliseconds). See below in section <em>About time to live</em> for
more details. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>transacted</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Specifies whether to use transacted mode for
sending/receiving messages using the InOnly <a shape="rect"
href="exchange-pattern.html" title="Exchange Pattern">Exchange Pattern</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>testConnectionOnStartup</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.1:</b> Specifies whether to test the
connection on startup. This ensures that when Camel starts that all the JMS
consumers have a valid connection to the JMS broker. If a connection cannot be
granted then Camel throws an exception on startup. This ensures that Camel is
not started with failed connections. From <b>Camel 2.8</b> onwards also the JMS
producers is tested as well. </td></tr></tbody
></table>
</div>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/jms.html
==============================================================================
--- websites/production/camel/content/jms.html (original)
+++ websites/production/camel/content/jms.html Thu Nov 22 13:22:12 2012
@@ -182,7 +182,7 @@ In Camel 2.8 onwards, the default settin
<h4><a shape="rect" name="JMS-Mostcommonlyusedoptions"></a>Most commonly used
options</h4>
<div class="confluenceTableSmall"><div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </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"> <tt>clientId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets the JMS client ID to use. Note that this value, if
specified, must be unique and can only be used by a single JMS connection
instance. It is typically only required for durable topic subscriptions. You
may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class
="confluenceTd"> Specifies the default number of concurrent consumers. From
<b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>disableReplyTo</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> If <tt>true</tt>, a producer will behave like a InOnly
exchange with the exception that <tt>JMSReplyTo</tt> header is sent out and not
be suppressed like in the case of <tt>InOnly</tt>. Like <tt>InOnly</tt> the
producer will not wait for a reply. A consumer with this flag will behave like
<tt>InOnly</tt>. This feature can be used to bridge <tt>InOut</tt> requests to
another queue so that a route on the other queue will send it´s response
directly back to the original <tt>JMSReplyTo</tt>. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>durableSubscriptionName</tt>
</td><td cols
pan="1" rowspan="1" class="confluenceTd"> <tt>null</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> The durable subscriber name for specifying
durable topic subscriptions. The <tt>clientId</tt> option <b>must</b> be
configured as well. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>maxConcurrentConsumers</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Specifies the maximum number of concurrent consumers.
From <b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>maxMessagesPerTask</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The number of messages per task. -1 is unlimited. If you
use a range for concurrent consumers (eg min < max), then this option can be
used to set a value to
eg <tt>100</tt> to control how fast the consumers will shrink when less work
is required. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>preserveMessageQos</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Set to <tt>true</tt>, if you want to send message using
the QoS settings specified on the message, instead of the QoS settings on the
JMS endpoint. The following three headers are considered <tt>JMSPriority</tt>,
<tt>JMSDeliveryMode</tt>, and <tt>JMSExpiration</tt>. You can provide all or
only some of them. If not provided, Camel will fall back to use the values from
the endpoint instead. So, when using this option, the headers override the
values from the endpoint. The <tt>explicitQosEnabled</tt> option, by contrast,
will only use options set on the endpoint, and not values from the message
header. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>replyTo
</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>null</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> Provides an explicit
ReplyTo destination, which overrides any incoming value of
<tt>Message.getJMSReplyTo()</tt>. If you do <a shape="rect"
href="request-reply.html" title="Request Reply">Request Reply</a> over JMS then
<b>make sure</b> to read the section <em>Request-reply over JMS</em> further
below for more details, and the <tt>replyToType</tt> option as well.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>replyToType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel
2.9:</b> Allows for explicitly specifying which kind of strategy to use for
replyTo queues when doing request/reply over JMS. Possible values are:
<tt>Temporary</tt>, <tt>Shared</tt>, or <tt>Exclusive</tt>. By default Camel
will use temporary queues. However if <tt>replyTo</
tt> has been configured, then <tt>Shared</tt> is used by default. This option
allows you to use exclusive queues instead of shared ones. See further below
for more details, and especially the notes about the implications if running in
a clustered environment, and the fact that <tt>Shared</tt> reply queues has
lower performance than its alternatives <tt>Temporary</tt> and
<tt>Exclusive</tt>. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>requestTimeout</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>20000</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Producer only:</b> The timeout for waiting for a reply
when using the InOut <a shape="rect" href="exchange-pattern.html"
title="Exchange Pattern">Exchange Pattern</a> (in milliseconds). The default is
20 seconds. See below in section <em>About time to live</em> for more details.
See also the <em>requestTimeoutCheckerInterval</em> option. </td></tr><tr><td
colspan="1" rowspan="
1" class="confluenceTd"> <tt>selector</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets the JMS Selector, which is an SQL 92 predicate that
is used to filter messages within the broker. You may have to encode special
characters such as = as %3D <b>Before Camel 2.3.0</b>, we don't support this
option in CamelConsumerTemplate </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeToLive</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When sending messages, specifies the time-to-live of the
message (in milliseconds). See below in section <em>About time to live</em> for
more details. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>transacted</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>false</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Specifies
w
hether to use transacted mode for sending/receiving messages using the InOnly
<a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange
Pattern</a>. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>testConnectionOnStartup</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.1:</b> Specifies whether to test the
connection on startup. This ensures that when Camel starts that all the JMS
consumers have a valid connection to the JMS broker. If a connection cannot be
granted then Camel throws an exception on startup. This ensures that Camel is
not started with failed connections. From <b>Camel 2.8</b> onwards also the JMS
producers is tested as well. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Option </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"> <tt>clientId</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Sets the JMS client ID to use. Note that this value, if
specified, must be unique and can only be used by a single JMS connection
instance. It is typically only required for durable topic subscriptions. You
may prefer to use <a shape="rect" class="external-link"
href="http://activemq.apache.org/virtual-destinations.html";>Virtual Topics</a>
instead. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1" class
="confluenceTd"> Specifies the default number of concurrent consumers. From
<b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. See also the <tt>maxMessagesPerTask</tt> option to
control dynamic scaling up/down of threads. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>disableReplyTo</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> If <tt>true</tt>, a producer will behave like
a InOnly exchange with the exception that <tt>JMSReplyTo</tt> header is sent
out and not be suppressed like in the case of <tt>InOnly</tt>. Like
<tt>InOnly</tt> the producer will not wait for a reply. A consumer with this
flag will behave like <tt>InOnly</tt>. This feature can be used to bridge
<tt>InOut</tt> requests to another queue so that a route on the other queue
will send it´s response directly back to the original <tt>JMSReplyTo</tt>.
</td></tr><tr><
td colspan="1" rowspan="1" class="confluenceTd">
<tt>durableSubscriptionName</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> The durable subscriber name for specifying durable topic
subscriptions. The <tt>clientId</tt> option <b>must</b> be configured as well.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>maxConcurrentConsumers</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>1</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Specifies the maximum number of concurrent consumers.
From <b>Camel 2.10.3</b> onwards this option can also be used when doing
request/reply over JMS. See also the <tt>maxMessagesPerTask</tt> option to
control dynamic scaling up/down of threads. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>maxMessagesPerTask</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>-1</tt> </td><td colspan="1"
rows
pan="1" class="confluenceTd"> The number of messages per task. -1 is
unlimited. If you use a range for concurrent consumers (eg min < max), then
this option can be used to set a value to eg <tt>100</tt> to control how fast
the consumers will shrink when less work is required. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <tt>preserveMessageQos</tt>
</td><td colspan="1" rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td
colspan="1" rowspan="1" class="confluenceTd"> Set to <tt>true</tt>, if you want
to send message using the QoS settings specified on the message, instead of the
QoS settings on the JMS endpoint. The following three headers are considered
<tt>JMSPriority</tt>, <tt>JMSDeliveryMode</tt>, and <tt>JMSExpiration</tt>. You
can provide all or only some of them. If not provided, Camel will fall back to
use the values from the endpoint instead. So, when using this option, the
headers override the values from the endpoint. The <tt>explicitQosEn
abled</tt> option, by contrast, will only use options set on the endpoint, and
not values from the message header. </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>replyTo</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> Provides an explicit ReplyTo destination, which overrides
any incoming value of <tt>Message.getJMSReplyTo()</tt>. If you do <a
shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a>
over JMS then <b>make sure</b> to read the section <em>Request-reply over
JMS</em> further below for more details, and the <tt>replyToType</tt> option as
well. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>replyToType</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel
2.9:</b> Allows for explicitly specifying which kind of strategy to use for
replyTo q
ueues when doing request/reply over JMS. Possible values are:
<tt>Temporary</tt>, <tt>Shared</tt>, or <tt>Exclusive</tt>. By default Camel
will use temporary queues. However if <tt>replyTo</tt> has been configured,
then <tt>Shared</tt> is used by default. This option allows you to use
exclusive queues instead of shared ones. See further below for more details,
and especially the notes about the implications if running in a clustered
environment, and the fact that <tt>Shared</tt> reply queues has lower
performance than its alternatives <tt>Temporary</tt> and <tt>Exclusive</tt>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>requestTimeout</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>20000</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<b>Producer only:</b> The timeout for waiting for a reply when using the InOut
<a shape="rect" href="exchange-pattern.html" title="Exchange Pattern">Exchange
Pattern</a> (in milliseconds). The
default is 20 seconds. See below in section <em>About time to live</em> for
more details. See also the <em>requestTimeoutCheckerInterval</em> option.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>selector</tt> </td><td colspan="1" rowspan="1" class="confluenceTd">
<tt>null</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Sets the
JMS Selector, which is an SQL 92 predicate that is used to filter messages
within the broker. You may have to encode special characters such as = as %3D
<b>Before Camel 2.3.0</b>, we don't support this option in
CamelConsumerTemplate </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>timeToLive</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>null</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> When sending messages, specifies the time-to-live of the
message (in milliseconds). See below in section <em>About time to live</em> for
more details. </td></tr><tr><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>transacted</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> <tt>false</tt> </td><td colspan="1"
rowspan="1" class="confluenceTd"> Specifies whether to use transacted mode for
sending/receiving messages using the InOnly <a shape="rect"
href="exchange-pattern.html" title="Exchange Pattern">Exchange Pattern</a>.
</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<tt>testConnectionOnStartup</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <tt>false</tt> </td><td colspan="1" rowspan="1"
class="confluenceTd"> <b>Camel 2.1:</b> Specifies whether to test the
connection on startup. This ensures that when Camel starts that all the JMS
consumers have a valid connection to the JMS broker. If a connection cannot be
granted then Camel throws an exception on startup. This ensures that Camel is
not started with failed connections. From <b>Camel 2.8</b> onwards also the JMS
producers is tested as well. </td></tr></tbody
></table>
</div>
