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 2015/07/21 17:18:58 UTC

svn commit: r959116 - in /websites/production/camel/content: cache/main.pageCache sjms-batch.html

Author: buildbot
Date: Tue Jul 21 15:18:57 2015
New Revision: 959116

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/sjms-batch.html

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

Modified: websites/production/camel/content/sjms-batch.html
==============================================================================
--- websites/production/camel/content/sjms-batch.html (original)
+++ websites/production/camel/content/sjms-batch.html Tue Jul 21 15:18:57 2015
@@ -100,7 +100,7 @@
 ]]></script>
 </div></div><p>You can include the optional <code>queue:</code> prefix, if you prefer:</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="brush: java; gutter: false; theme: Default" type="syntaxhighlighter"><![CDATA[sjms:queue:FOO.BAR]]></script>
-</div></div><p>Topic consumption is not supported, as there is no advantage to using batch consumption within that context. Topic messages are usually non-persistent, and loss is acceptable. If consumed within a transaction that fails, a topic message will likely not be redelivered by the broker.</p><h3 id="SJMSBatch-ComponentOptionsandConfigurations">Component Options and Configurations</h3><p>The SJMS Batch Component supports the following configuration options:</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Required</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>aggregationStrategy</code></p></td><td colspan="1" rowspan="1" class="conflu
 enceTd"><p>&#160;<img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code><code>null</code></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A reference to an <code>AggregationStrategy</code> in the Camel registry (e.g. <code>#myAggregationStrategy</code>)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code><code>completionSize</code></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>200<br clear="none"></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The size of the batch to aggregate.</p><p>Care should be taken to ensure that this is not larger than the JMS consumer's prefetch buffer, or the maximum page size for a queu
 e on the broker; either of these could cause the consumer to hang if no timeout is used.</p><p>A value of 0 or less indicates that <code>completionTimeout</code> only should be used.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>completionTimeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>500</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum time to wait from the receipt of the first message before emitting the Exchange.</p><p>A value of 0 or less indicates that <code>completionSize</code> only should be used.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>pollDuration</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum length of a ca
 ll to <code>MessageConsumer.receive()</code>. The time remaining before timeout takes precedence within a batch.</p><p>This value is effectively the poll time between batches.</p></td></tr></tbody></table></div></div><p>The <code>completionSize</code> endpoint attribute is used in conjunction with <code>completionTimeout</code>, where the first condition to be met will cause the aggregated <code>Exchange</code> to be emitted down the route.</p><p>&#160;</p></div>
+</div></div><p>Topic consumption is not supported, as there is no advantage to using batch consumption within that context. Topic messages are usually non-persistent, and loss is acceptable. If consumed within a transaction that fails, a topic message will likely not be redelivered by the broker. A plain <a shape="rect" href="sjms.html">SJMS</a> consumer endpoint can be used in conjunction with a regular non-persistence backed <a shape="rect" href="aggregator2.html">aggregator</a> in this scenario.</p><h3 id="SJMSBatch-ComponentOptionsandConfigurations">Component Options and Configurations</h3><p>The SJMS Batch Component supports the following configuration options:</p><div class="confluenceTableSmall"><div class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Option</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Required</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Default Value</p></th><th colsp
 an="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>aggregationStrategy</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;<img class="emoticon emoticon-tick" src="https://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/check.png" data-emoticon-name="tick" alt="(tick)"></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code><code>null</code></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>A reference to an <code>AggregationStrategy</code> in the Camel registry (e.g. <code>#myAggregationStrategy</code>)</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code><code>completionSize</code></code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>200<br clear="none"></code></p></td><td colspan="1" row
 span="1" class="confluenceTd"><p>The size of the batch to aggregate.</p><p>Care should be taken to ensure that this is not larger than the JMS consumer's prefetch buffer, or the maximum page size for a queue on the broker; either of these could cause the consumer to hang if no timeout is used.</p><p>A value of 0 or less indicates that <code>completionTimeout</code> only should be used.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>completionTimeout</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>500</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum time to wait from the receipt of the first message before emitting the Exchange.</p><p>A value of 0 or less indicates that <code>completionSize</code> only should be used.</p></td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd"><p><code>pollDuration</code></p></td><td colspan="1" r
 owspan="1" class="confluenceTd"><p>&#160;</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><code>1000</code></p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>The maximum length of a call to <code>MessageConsumer.receive()</code>. The time remaining before timeout takes precedence within a batch.</p><p>This value is effectively the poll time between batches.</p></td></tr></tbody></table></div></div><p>The <code>completionSize</code> endpoint attribute is used in conjunction with <code>completionTimeout</code>, where the first condition to be met will cause the aggregated <code>Exchange</code> to be emitted down the route.</p><p>&#160;</p></div>
         </td>
         <td valign="top">
           <div class="navigation">