You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by bu...@apache.org on 2012/11/20 15:23:16 UTC
svn commit: r838928 [1/2] - in /websites/production/camel/content:
book-component-appendix.html book-in-one-page.html cache/main.pageCache
camel-2110-release.html jms.html
Author: buildbot
Date: Tue Nov 20 14:23:15 2012
New Revision: 838928
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/camel-2110-release.html
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 Tue Nov 20 14:23:15 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. </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="c
onfluenceTd"> 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. </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 col
span="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 in
coming 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 no
tes 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, whic
h 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 colspa
n="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 Camel 2.11 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 colspan="1" r
owspan="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 Camel 2.11 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 col
span="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 confi
gured, 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="confluen
ceTd"> <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 tran
sacted 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>
@@ -9207,7 +9207,7 @@ from(<span class="code-quote">"jms:SomeQ
<p>Camel offers a number of options to configure request/reply over JMS that influence performance and clustered environments. The table below summaries the options.</p>
<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"> Performance </th><th colspan="1" rowspan="1" class="confluenceTh"> Cluster </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Temporary</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A temporary queue is used as reply queue, and automatic created by Camel. To use this do <b>not</b> specify a replyTo queue name. And you can optionally configure <tt>replyToType=Temporary</tt> to make it stand out that temporary queues are in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Shared</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Slow </td><td colspan="1" rowspan="1" class="conflue
nceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A shared persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you can optionally configure <tt>replyToType=Shared</tt> to make it stand out that shared queues are in use. A shared queue can be used in a clustered environment with multiple nodes running this Camel application at the same time. All using the same shared reply queue. This is possible because JMS Message selectors are used to correlate expected reply messages; this impacts performance though. JMS Message selectors is slower, and therefore not as fast as <tt>Temporary</tt> or <tt>Exclusive</tt> queues. See further below how to tweak this for better performance. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Exclusive</tt> </td><td colspan="1" rowspan="1" class="confluenceT
d"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> No </td><td colspan="1" rowspan="1" class="confluenceTd"> An exclusive persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you <b>must</b> configure <tt>replyToType=Exclusive</tt> to instruct Camel to use exclusive queues, as <tt>Shared</tt> is used by default, if a <tt>replyTo</tt> queue name was configured. When using exclusive reply queues, then JMS Message selectors are <b>not</b> in use, and therefore other applications must not use this queue as well. An exclusive queue <b>cannot</b> be used in a clustered environment with multiple nodes running this Camel application at the same time; as we do not have control if the reply queue comes back to the same node that sent the request message; that is why shared queues use JMS Message selectors to make sure
of this. </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"> Performance </th><th colspan="1" rowspan="1" class="confluenceTh"> Cluster </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Temporary</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A temporary queue is used as reply queue, and automatic created by Camel. To use this do <b>not</b> specify a replyTo queue name. And you can optionally configure <tt>replyToType=Temporary</tt> to make it stand out that temporary queues are in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Shared</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Slow </td><td colspan="1" rowspan="1" class="conflue
nceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A shared persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you can optionally configure <tt>replyToType=Shared</tt> to make it stand out that shared queues are in use. A shared queue can be used in a clustered environment with multiple nodes running this Camel application at the same time. All using the same shared reply queue. This is possible because JMS Message selectors are used to correlate expected reply messages; this impacts performance though. JMS Message selectors is slower, and therefore not as fast as <tt>Temporary</tt> or <tt>Exclusive</tt> queues. See further below how to tweak this for better performance. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Exclusive</tt> </td><td colspan="1" rowspan="1" class="confluenceT
d"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> No </td><td colspan="1" rowspan="1" class="confluenceTd"> An exclusive persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you <b>must</b> configure <tt>replyToType=Exclusive</tt> to instruct Camel to use exclusive queues, as <tt>Shared</tt> is used by default, if a <tt>replyTo</tt> queue name was configured. When using exclusive reply queues, then JMS Message selectors are <b>not</b> in use, and therefore other applications must not use this queue as well. An exclusive queue <b>cannot</b> be used in a clustered environment with multiple nodes running this Camel application at the same time; as we do not have control if the reply queue comes back to the same node that sent the request message; that is why shared queues use JMS Message selectors to make sure
of this. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Allows to process reply messages concurrently using concurrent message listeners in use. You can specify a range using the <tt>concurrentConsumers</tt> and <tt>maxConcurrentConsumers</tt> options. <b>Notice:</b> That using <tt>Shared</tt> reply queues may not work as well with concurrent listeners, so use this option with care.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>maxConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Allows to process reply messages concurrently using concurrent message list
eners in use. You can specify a range using the <tt>concurrentConsumers</tt> and <tt>maxConcurrentConsumers</tt> options. <b>Notice:</b> That using <tt>Shared</tt> reply queues may not work as well with concurrent listeners, so use this option with care. </td></tr></tbody></table>
</div>
</div>
@@ -9229,6 +9229,17 @@ from(xxx)
<p>In this route we instruct Camel to route replies <a shape="rect" href="async.html" title="Async">asynchronously</a> using a thread pool with 5 threads.</p>
+<p>From Camel 2.11 onwards you can now configure the listener to use concurrent threads using the <tt>concurrentConsumers</tt> and <tt>maxConcurrentConsumers</tt> options. This allows you to easier configure this in Camel as shown below:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java">
+from(xxx)
+.inOut().to(<span class="code-quote">"activemq:queue:foo?concurrentConsumers=5"</span>)
+.to(yyy)
+.to(zzz);
+</pre>
+</div></div>
+
+
<h4><a shape="rect" name="BookComponentAppendix-RequestreplyoverJMSandusingasharedfixedreplyqueue"></a>Request-reply over JMS and using a shared fixed reply queue</h4>
<p>If you use a fixed reply queue when doing <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> over JMS as shown in the example below, then pay attention.</p>
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 Tue Nov 20 14:23:15 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. </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="c
onfluenceTd"> 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. </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 col
span="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 in
coming 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 no
tes 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, whic
h 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 colspa
n="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 Camel 2.11 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 colspan="1" r
owspan="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 Camel 2.11 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 col
span="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 confi
gured, 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="confluen
ceTd"> <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 tran
sacted 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>
@@ -29443,7 +29443,7 @@ from(<span class="code-quote">"jms:SomeQ
<p>Camel offers a number of options to configure request/reply over JMS that influence performance and clustered environments. The table below summaries the options.</p>
<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"> Performance </th><th colspan="1" rowspan="1" class="confluenceTh"> Cluster </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Temporary</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A temporary queue is used as reply queue, and automatic created by Camel. To use this do <b>not</b> specify a replyTo queue name. And you can optionally configure <tt>replyToType=Temporary</tt> to make it stand out that temporary queues are in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Shared</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Slow </td><td colspan="1" rowspan="1" class="conflue
nceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A shared persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you can optionally configure <tt>replyToType=Shared</tt> to make it stand out that shared queues are in use. A shared queue can be used in a clustered environment with multiple nodes running this Camel application at the same time. All using the same shared reply queue. This is possible because JMS Message selectors are used to correlate expected reply messages; this impacts performance though. JMS Message selectors is slower, and therefore not as fast as <tt>Temporary</tt> or <tt>Exclusive</tt> queues. See further below how to tweak this for better performance. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Exclusive</tt> </td><td colspan="1" rowspan="1" class="confluenceT
d"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> No </td><td colspan="1" rowspan="1" class="confluenceTd"> An exclusive persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you <b>must</b> configure <tt>replyToType=Exclusive</tt> to instruct Camel to use exclusive queues, as <tt>Shared</tt> is used by default, if a <tt>replyTo</tt> queue name was configured. When using exclusive reply queues, then JMS Message selectors are <b>not</b> in use, and therefore other applications must not use this queue as well. An exclusive queue <b>cannot</b> be used in a clustered environment with multiple nodes running this Camel application at the same time; as we do not have control if the reply queue comes back to the same node that sent the request message; that is why shared queues use JMS Message selectors to make sure
of this. </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"> Performance </th><th colspan="1" rowspan="1" class="confluenceTh"> Cluster </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Temporary</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A temporary queue is used as reply queue, and automatic created by Camel. To use this do <b>not</b> specify a replyTo queue name. And you can optionally configure <tt>replyToType=Temporary</tt> to make it stand out that temporary queues are in use. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Shared</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Slow </td><td colspan="1" rowspan="1" class="conflue
nceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> A shared persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you can optionally configure <tt>replyToType=Shared</tt> to make it stand out that shared queues are in use. A shared queue can be used in a clustered environment with multiple nodes running this Camel application at the same time. All using the same shared reply queue. This is possible because JMS Message selectors are used to correlate expected reply messages; this impacts performance though. JMS Message selectors is slower, and therefore not as fast as <tt>Temporary</tt> or <tt>Exclusive</tt> queues. See further below how to tweak this for better performance. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>Exclusive</tt> </td><td colspan="1" rowspan="1" class="confluenceT
d"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> No </td><td colspan="1" rowspan="1" class="confluenceTd"> An exclusive persistent queue is used as reply queue. The queue must be created beforehand, although some brokers can create them on the fly such as Apache ActiveMQ. To use this you must specify the replyTo queue name. And you <b>must</b> configure <tt>replyToType=Exclusive</tt> to instruct Camel to use exclusive queues, as <tt>Shared</tt> is used by default, if a <tt>replyTo</tt> queue name was configured. When using exclusive reply queues, then JMS Message selectors are <b>not</b> in use, and therefore other applications must not use this queue as well. An exclusive queue <b>cannot</b> be used in a clustered environment with multiple nodes running this Camel application at the same time; as we do not have control if the reply queue comes back to the same node that sent the request message; that is why shared queues use JMS Message selectors to make sure
of this. </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>concurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Allows to process reply messages concurrently using concurrent message listeners in use. You can specify a range using the <tt>concurrentConsumers</tt> and <tt>maxConcurrentConsumers</tt> options. <b>Notice:</b> That using <tt>Shared</tt> reply queues may not work as well with concurrent listeners, so use this option with care.</td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"> <tt>maxConcurrentConsumers</tt> </td><td colspan="1" rowspan="1" class="confluenceTd"> Fast </td><td colspan="1" rowspan="1" class="confluenceTd"> Yes </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>Camel 2.11:</b> Allows to process reply messages concurrently using concurrent message list
eners in use. You can specify a range using the <tt>concurrentConsumers</tt> and <tt>maxConcurrentConsumers</tt> options. <b>Notice:</b> That using <tt>Shared</tt> reply queues may not work as well with concurrent listeners, so use this option with care. </td></tr></tbody></table>
</div>
</div>
@@ -29465,6 +29465,17 @@ from(xxx)
<p>In this route we instruct Camel to route replies <a shape="rect" href="async.html" title="Async">asynchronously</a> using a thread pool with 5 threads.</p>
+<p>From Camel 2.11 onwards you can now configure the listener to use concurrent threads using the <tt>concurrentConsumers</tt> and <tt>maxConcurrentConsumers</tt> options. This allows you to easier configure this in Camel as shown below:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<pre class="code-java">
+from(xxx)
+.inOut().to(<span class="code-quote">"activemq:queue:foo?concurrentConsumers=5"</span>)
+.to(yyy)
+.to(zzz);
+</pre>
+</div></div>
+
+
<h4><a shape="rect" name="BookInOnePage-RequestreplyoverJMSandusingasharedfixedreplyqueue"></a>Request-reply over JMS and using a shared fixed reply queue</h4>
<p>If you use a fixed reply queue when doing <a shape="rect" href="request-reply.html" title="Request Reply">Request Reply</a> over JMS as shown in the example below, then pay attention.</p>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/camel-2110-release.html
==============================================================================
--- websites/production/camel/content/camel-2110-release.html (original)
+++ websites/production/camel/content/camel-2110-release.html Tue Nov 20 14:23:15 2012
@@ -84,7 +84,8 @@
<p>Welcome to the 2.11.0 release with approximately XXX issues resolved - including new features, improvements, and bug fixes, such as: </p>
-<ul><li>Added <a shape="rect" href="binding.html" title="Binding">Binding</a> support, so it is easy to combine things like a <a shape="rect" href="data-format.html" title="Data Format">Data Format</a> to an <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> for easier composition of routes.</li><li>Added support for SOAP 1.2 in <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format.</li><li><a shape="rect" href="cache.html" title="Cache">Cache</a> operation for add/update now supports expiry headers to control time to live/idle/eternal.</li><li>Added <tt>allowNullBody</tt> option to <a shape="rect" href="jms.html" title="JMS">JMS</a> to configure whether sending messages with no body is allowed.</li><li>Added <tt>connectOnStartup</tt> option to <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> to allow to connect on demand, to avoid having Hadoop block for long time connecting to the HDFS cluster, as it has a hardcoded 15 minute retry mechan
ism.</li><li>Added support for daily and weekly trends to <a shape="rect" href="twitter.html" title="Twitter">Twitter</a> component.</li><li>The <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> now generates projects without any license headers.</li><li>Added 'rejectOld' option to the <a shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to prevent out of order messages from being delivered after capacity/timeout events occur</li><li>Further optimized <a shape="rect" href="xpath.html" title="XPath">XPath</a> under concurrent load, and as well ensured resources are cleaned up eagerly</li><li>Added options <tt>allowNullBody</tt> and <tt>readLockMinLength</tt> to the <a shape="rect" href="file2.html" title="File2">File</a> and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components.</li><li>Made <tt>changed</tt> read lock strategy on <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> g
o faster (eg when the FTP server has a lot of files in the directory) if you enable the <tt>fastExistsCheck=true</tt> option as well. Notice that some FTP server may not support this.</li><li><a shape="rect" href="hl7.html" title="HL7">HL7</a> moves to HAPI 2.0 and supports using a dedicated Parser instance in the <a shape="rect" href="hl7.html" title="HL7">HL7</a> MLLP codec and DataFormat. Added "Terser" language and expression to be able to extract fields from a parsed message. <a shape="rect" href="hl7.html" title="HL7">HL7</a> now uses Apache Mina 2.x.</li><li>Add an option <tt>HttpMethodRestrict</tt> to restrict HTTP method in <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> and <a shape="rect" href="servlet.html" title="SERVLET">SERVLET</a></li><li>Add support for selection of <a shape="rect" href="direct-vm.html" title="Direct-VM">Direct-VM</a> consumers by using ant-like path expression.</li><li>The <a shape="rect" href="pojo-producing.html" title="POJO Pro
ducing">POJO Producing</a>, and <a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a> with @Consume, @Produce, @EndpointInject now supports a new {{property} attribute to get the endpoint configuration from a bean property (eg using a getter method); this allows you to configure this on the bean using conventional bean configuration.</li><li>Testing with <tt>camel-test-blueprint</tt> on Windows no longer tries to cleanup after testing taking up 5 seconds and logging WARNs.</li><li>The <a shape="rect" href="file2.html" title="File2">File</a>, and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components now support <tt>fileExist=Move</tt> option to move any existing files before writing a file.</li><li>Added option <tt>loadStatisticsEnabled</tt> on <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> to allow to disable load statistics if not needed (avoids a background thread being in use, to calculate the load stats).</
li><li>Enabled "lazy connections" for <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> providers via the <tt>testConnectionOnStartup</tt> option</li><li>Added a connection monitor to detect and fix dropped <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> consumer connections at configurable <tt>connectionPollDelay</tt> intervals</li><li>Added an <tt>org.apache.camel.builder.ExchangeBuilder</tt> to build the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> using a builder pattern.</li><li>The <a shape="rect" href="camel-run-maven-goal.html" title="Camel Run Maven Goal">Camel Run Maven Goal</a> can now run <a shape="rect" href="cdi.html" title="CDI">CDI</a> applications.</li><li>The Camel <a shape="rect" href="cdi.html" title="CDI">CDI</a> component has improved a lot.</li><li>Added option <tt>allowRedeliveryWhileStopping</tt> to <a shape="rect" href="dead-letter-channel.html" title="Dead Letter Channel">error handlers</a> to control if redelivery
is allowed during stopping/shutting down Camel or the route(s). Turning this option <tt>false</tt> allows to stop quicker by rejecting redelivery attempts.</li><li>Added support for specifying user info in Camel <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> urls, which contains the @ sign; now the @ sign can be given as is; without being encoded to %40.</li><li>Added robust connection support for <a shape="rect" href="jmx.html" title="JMX">JMX</a>. Optional <tt>testConnectionOnStartup</tt> allows a JMX consumer to attach to a JMX server that becomes available <em>after</em> the JMX endpoint starts; <tt>reconnectOnConnectionFailure</tt> enables re-connection of failed JMX connections.</li><li><a shape="rect" href="jaxb.html" title="JAXB">JAXB</a> and <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format now supports controlling namespace prefix mappings when marshalling (eg to avoid prefixes such as ns2, ns3, ns4 etc.)</li><li>Added support
for using raw uris when <a shape="rect" href="component.html" title="Component">Component</a>s create <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a>s. This gives component writers full power in case their component has special syntax/notation for endpoint uri configurations.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s configured with custom <tt>AggregationStrategy</tt> will now strict check the custom strategy exists in the <a shape="rect" href="registry.html" title="Registry">Registry</a> and no longer fallback and use a default strategy if not.</li><li>Camel now logs on shutdown if any thread pools hasn't been properly shutdown, and will shutdown them as fail safe (can only be done for the thread pools Camel manages).</li><li>The buffer size of <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a> is now configurable.</li><li>Improved startup performance.</li><li>Added <a shape="rect" href="jms.html" title
="JMS">JMS</a> URI option <tt>messageListenerContainerFactoryRef</tt> which allows you to specify a <tt>MessageListenerContainerFactory</tt> to determine what <tt>org.springframework.jms.listener.AbstractMessageListenerContainer</tt> to use to consume messages.</li><li><a shape="rect" href="mqtt.html" title="MQTT">MQTT</a> producer now leverages the <a shape="rect" href="asynchronous-routing-engine.html" title="Asynchronous Routing Engine">Asynchronous Routing Engine</a></li><li>The <a shape="rect" href="netty.html" title="Netty">Netty</a> producer scales up and down much better by leveraging a channel pool.</li><li>Added new <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> for creating Camel and Groovy applications.</li><li>Camel now injects <tt>CamelContext</tt> on <tt>Language</tt> and <tt>DataFormat</tt> that implements <tt>CamelContextAware</tt></li><li>Thread pools in Camel with <tt>maximumQueueSize</tt> of 0
or negative will now not use a worker queue but do direct hand-over to thread instead.</li><li><a shape="rect" href="simple.html" title="Simple">Simple</a> unary operators for inc and dec must now have function on left hand side, to be parsed as unary function. Otherwise its now regarded as literal.</li><li>Custom assigned id's on Camel <a shape="rect" href="routes.html" title="Routes">Routes</a> is now validated on starting the routes, that they must be unique within the same CamelContext.</li><li>Added <tt>AbstractListAggregationStrategy</tt> abstract class to make it easier to <a shape="rect" href="aggregator2.html" title="Aggregator2">aggregate</a> into a List<V> using a custom <tt>AggregationStrategy</tt>.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s which support using <tt>AggregationStrategy</tt> now control the lifecycle of the strategy; allowing end users to do custom logic in the start/stop methods of their strategy implementation.</li><li>Add
ed option <tt>includeSentJMSMessageID</tt> to <a shape="rect" href="jms.html" title="JMS">JMS</a> to allow to enrich Camel Message with the actual JMSMessageID for the sent message. Can be used by end users for logging purpose etc.</li><li>Added option <tt>allowShortLines</tt> and <tt>ignoreExtraColumns</tt> to <a shape="rect" href="flatpack-dataformat.html" title="Flatpack DataFormat">Flatpack data format</a>.</li><li><a shape="rect" href="mail.html" title="Mail">Mail</a> consumer now supports using search terms to filter mails by terms such as subject, from, body, sent date etc.</li><li>The cached script file in the <a shape="rect" href="language.html" title="Language">Language</a> component can now be cleared via JMX.</li><li>improved the karaf context-info command by adding a verbose mode to view endpoints list (now hidden by default) and adding stats on the number of active/inactive routes</li><li>Added support for <tt>UpdateList</tt>, <tt>DeleteList</tt> and <tt>Execut
orType</tt> to <a shape="rect" href="mybatis.html" title="MyBatis">MyBatis</a> component.</li></ul>
+<ul><li>Added <a shape="rect" href="binding.html" title="Binding">Binding</a> support, so it is easy to combine things like a <a shape="rect" href="data-format.html" title="Data Format">Data Format</a> to an <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> for easier composition of routes.</li><li>Added support for SOAP 1.2 in <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format.</li><li><a shape="rect" href="cache.html" title="Cache">Cache</a> operation for add/update now supports expiry headers to control time to live/idle/eternal.</li><li>Added <tt>allowNullBody</tt> option to <a shape="rect" href="jms.html" title="JMS">JMS</a> to configure whether sending messages with no body is allowed.</li><li>Added <tt>connectOnStartup</tt> option to <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a> to allow to connect on demand, to avoid having Hadoop block for long time connecting to the HDFS cluster, as it has a hardcoded 15 minute retry mechan
ism.</li><li>Added support for daily and weekly trends to <a shape="rect" href="twitter.html" title="Twitter">Twitter</a> component.</li><li>The <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> now generates projects without any license headers.</li><li>Added 'rejectOld' option to the <a shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to prevent out of order messages from being delivered after capacity/timeout events occur</li><li>Further optimized <a shape="rect" href="xpath.html" title="XPath">XPath</a> under concurrent load, and as well ensured resources are cleaned up eagerly</li><li>Added options <tt>allowNullBody</tt> and <tt>readLockMinLength</tt> to the <a shape="rect" href="file2.html" title="File2">File</a> and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components.</li><li>Made <tt>changed</tt> read lock strategy on <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> g
o faster (eg when the FTP server has a lot of files in the directory) if you enable the <tt>fastExistsCheck=true</tt> option as well. Notice that some FTP server may not support this.</li><li><a shape="rect" href="hl7.html" title="HL7">HL7</a> moves to HAPI 2.0 and supports using a dedicated Parser instance in the <a shape="rect" href="hl7.html" title="HL7">HL7</a> MLLP codec and DataFormat. Added "Terser" language and expression to be able to extract fields from a parsed message. <a shape="rect" href="hl7.html" title="HL7">HL7</a> now uses Apache Mina 2.x.</li><li>Add an option <tt>HttpMethodRestrict</tt> to restrict HTTP method in <a shape="rect" href="jetty.html" title="Jetty">Jetty</a> and <a shape="rect" href="servlet.html" title="SERVLET">SERVLET</a></li><li>Add support for selection of <a shape="rect" href="direct-vm.html" title="Direct-VM">Direct-VM</a> consumers by using ant-like path expression.</li><li>The <a shape="rect" href="pojo-producing.html" title="POJO Pro
ducing">POJO Producing</a>, and <a shape="rect" href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a> with @Consume, @Produce, @EndpointInject now supports a new {{property} attribute to get the endpoint configuration from a bean property (eg using a getter method); this allows you to configure this on the bean using conventional bean configuration.</li><li>Testing with <tt>camel-test-blueprint</tt> on Windows no longer tries to cleanup after testing taking up 5 seconds and logging WARNs.</li><li>The <a shape="rect" href="file2.html" title="File2">File</a>, and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components now support <tt>fileExist=Move</tt> option to move any existing files before writing a file.</li><li>Added option <tt>loadStatisticsEnabled</tt> on <a shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> to allow to disable load statistics if not needed (avoids a background thread being in use, to calculate the load stats).</
li><li>Enabled "lazy connections" for <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> providers via the <tt>testConnectionOnStartup</tt> option</li><li>Added a connection monitor to detect and fix dropped <a shape="rect" href="xmpp.html" title="XMPP">XMPP</a> consumer connections at configurable <tt>connectionPollDelay</tt> intervals</li><li>Added an <tt>org.apache.camel.builder.ExchangeBuilder</tt> to build the <a shape="rect" href="exchange.html" title="Exchange">Exchange</a> using a builder pattern.</li><li>The <a shape="rect" href="camel-run-maven-goal.html" title="Camel Run Maven Goal">Camel Run Maven Goal</a> can now run <a shape="rect" href="cdi.html" title="CDI">CDI</a> applications.</li><li>The Camel <a shape="rect" href="cdi.html" title="CDI">CDI</a> component has improved a lot.</li><li>Added option <tt>allowRedeliveryWhileStopping</tt> to <a shape="rect" href="dead-letter-channel.html" title="Dead Letter Channel">error handlers</a> to control if redelivery
is allowed during stopping/shutting down Camel or the route(s). Turning this option <tt>false</tt> allows to stop quicker by rejecting redelivery attempts.</li><li>Added support for specifying user info in Camel <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> urls, which contains the @ sign; now the @ sign can be given as is; without being encoded to %40.</li><li>Added robust connection support for <a shape="rect" href="jmx.html" title="JMX">JMX</a>. Optional <tt>testConnectionOnStartup</tt> allows a JMX consumer to attach to a JMX server that becomes available <em>after</em> the JMX endpoint starts; <tt>reconnectOnConnectionFailure</tt> enables re-connection of failed JMX connections.</li><li><a shape="rect" href="jaxb.html" title="JAXB">JAXB</a> and <a shape="rect" href="soap.html" title="SOAP">SOAP</a> data format now supports controlling namespace prefix mappings when marshalling (eg to avoid prefixes such as ns2, ns3, ns4 etc.)</li><li>Added support
for using raw uris when <a shape="rect" href="component.html" title="Component">Component</a>s create <a shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a>s. This gives component writers full power in case their component has special syntax/notation for endpoint uri configurations.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s configured with custom <tt>AggregationStrategy</tt> will now strict check the custom strategy exists in the <a shape="rect" href="registry.html" title="Registry">Registry</a> and no longer fallback and use a default strategy if not.</li><li>Camel now logs on shutdown if any thread pools hasn't been properly shutdown, and will shutdown them as fail safe (can only be done for the thread pools Camel manages).</li><li>The buffer size of <a shape="rect" href="stream-caching.html" title="Stream caching">Stream caching</a> is now configurable.</li><li>Improved startup performance.</li><li>Added <a shape="rect" href="jms.html" title
="JMS">JMS</a> URI option <tt>messageListenerContainerFactoryRef</tt> which allows you to specify a <tt>MessageListenerContainerFactory</tt> to determine what <tt>org.springframework.jms.listener.AbstractMessageListenerContainer</tt> to use to consume messages.</li><li><a shape="rect" href="mqtt.html" title="MQTT">MQTT</a> producer now leverages the <a shape="rect" href="asynchronous-routing-engine.html" title="Asynchronous Routing Engine">Asynchronous Routing Engine</a></li><li>The <a shape="rect" href="netty.html" title="Netty">Netty</a> producer scales up and down much better by leveraging a channel pool.</li><li>Added new <a shape="rect" href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven Archetypes</a> for creating Camel and Groovy applications.</li><li>Camel now injects <tt>CamelContext</tt> on <tt>Language</tt> and <tt>DataFormat</tt> that implements <tt>CamelContextAware</tt></li><li>Thread pools in Camel with <tt>maximumQueueSize</tt> of 0
or negative will now not use a worker queue but do direct hand-over to thread instead.</li><li><a shape="rect" href="simple.html" title="Simple">Simple</a> unary operators for inc and dec must now have function on left hand side, to be parsed as unary function. Otherwise its now regarded as literal.</li><li>Custom assigned id's on Camel <a shape="rect" href="routes.html" title="Routes">Routes</a> is now validated on starting the routes, that they must be unique within the same CamelContext.</li><li>Added <tt>AbstractListAggregationStrategy</tt> abstract class to make it easier to <a shape="rect" href="aggregator2.html" title="Aggregator2">aggregate</a> into a List<V> using a custom <tt>AggregationStrategy</tt>.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s which support using <tt>AggregationStrategy</tt> now control the lifecycle of the strategy; allowing end users to do custom logic in the start/stop methods of their strategy implementation.</li><li>Add
ed option <tt>includeSentJMSMessageID</tt> to <a shape="rect" href="jms.html" title="JMS">JMS</a> to allow to enrich Camel Message with the actual JMSMessageID for the sent message. Can be used by end users for logging purpose etc.</li><li>Added option <tt>allowShortLines</tt> and <tt>ignoreExtraColumns</tt> to <a shape="rect" href="flatpack-dataformat.html" title="Flatpack DataFormat">Flatpack data format</a>.</li><li><a shape="rect" href="mail.html" title="Mail">Mail</a> consumer now supports using search terms to filter mails by terms such as subject, from, body, sent date etc.</li><li>The cached script file in the <a shape="rect" href="language.html" title="Language">Language</a> component can now be cleared via JMX.</li><li>improved the karaf context-info command by adding a verbose mode to view endpoints list (now hidden by default) and adding stats on the number of active/inactive routes</li><li>Added support for <tt>UpdateList</tt>, <tt>DeleteList</tt> and <tt>Execut
orType</tt> to <a shape="rect" href="mybatis.html" title="MyBatis">MyBatis</a> component.</li><li>Added support for easier configuration of using concurrent message listener consumer when doing request/reply over <a shape="rect" href="jms.html" title="JMS">JMS</a>, by leveraging the existing <tt>concurrentConsumers</tt> and <tt>maxConcurrentConsumers</tt> options.</li></ul>
+
<h3><a shape="rect" name="Camel2.11.0Release-Fixedissues"></a>Fixed issues</h3>