Author: buildbot
Date: Tue Oct 9 14:19:21 2012
New Revision: 834546
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/book-cookbook.html
websites/production/camel/content/book-in-one-page.html
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/parallel-processing-and-ordering.html
Modified: websites/production/camel/content/book-cookbook.html
==============================================================================
--- websites/production/camel/content/book-cookbook.html (original)
+++ websites/production/camel/content/book-cookbook.html Tue Oct 9 14:19:21
2012
@@ -2690,7 +2690,7 @@ from(<span class="code-quote">"activemq:
<p>This topic is large and diverse with lots of different requirements; but
from a high level here are our recommendations on parallel processing, ordering
and concurrency</p>
-<ul><li>for distributed locking, use a database by default, they are very good
at it <img align="middle" class="emoticon"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/smile.gif";
height="20" width="20" alt="" border="0"></li><li>to preserve ordering across a
JMS queue consider using <a shape="rect" class="external-link"
href="http://activemq.apache.org/exclusive-consumer.html";>Exclusive
Consumers</a> in the <a shape="rect" href="activemq.html"
title="ActiveMQ">ActiveMQ</a> component</li><li>even better are <a shape="rect"
class="external-link"
href="http://activemq.apache.org/message-groups.html";>Message Groups</a> which
allows you to preserve ordering across messages while still offering
parallelisation via the <b>JMSXGrouopID</b> header to determine what can be
parallelized</li><li>if you receive messages out of order you could use the <a
shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to put
them back together again</li></ul>
+<ul><li>for distributed locking, use a database by default, they are very good
at it <img align="middle" class="emoticon"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/smile.gif";
height="20" width="20" alt="" border="0"></li><li>to preserve ordering across a
JMS queue consider using <a shape="rect" class="external-link"
href="http://activemq.apache.org/exclusive-consumer.html";>Exclusive
Consumers</a> in the <a shape="rect" href="activemq.html"
title="ActiveMQ">ActiveMQ</a> component</li><li>even better are <a shape="rect"
class="external-link"
href="http://activemq.apache.org/message-groups.html";>Message Groups</a> which
allows you to preserve ordering across messages while still offering
parallelisation via the <b>JMSXGroupID</b> header to determine what can be
parallelized</li><li>if you receive messages out of order you could use the <a
shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to put
them back together again</li></ul>
<p>A good rule of thumb to help reduce ordering problems is to make sure each
single can be processed as an atomic unit in parallel (either without
concurrency issues or using say, database locking); or if it can't, use a <a
shape="rect" class="external-link"
href="http://activemq.apache.org/message-groups.html";>Message Group</a> to
relate the messages together which need to be processed in order by a single
thread.</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 Oct 9 14:19:21
2012
@@ -3865,7 +3865,7 @@ from(<span class="code-quote">"activemq:
<p>This topic is large and diverse with lots of different requirements; but
from a high level here are our recommendations on parallel processing, ordering
and concurrency</p>
-<ul><li>for distributed locking, use a database by default, they are very good
at it <img align="middle" class="emoticon"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/smile.gif";
height="20" width="20" alt="" border="0"></li><li>to preserve ordering across a
JMS queue consider using <a shape="rect" class="external-link"
href="http://activemq.apache.org/exclusive-consumer.html";>Exclusive
Consumers</a> in the <a shape="rect" href="activemq.html"
title="ActiveMQ">ActiveMQ</a> component</li><li>even better are <a shape="rect"
class="external-link"
href="http://activemq.apache.org/message-groups.html";>Message Groups</a> which
allows you to preserve ordering across messages while still offering
parallelisation via the <b>JMSXGrouopID</b> header to determine what can be
parallelized</li><li>if you receive messages out of order you could use the <a
shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to put
them back together again</li></ul>
+<ul><li>for distributed locking, use a database by default, they are very good
at it <img align="middle" class="emoticon"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/smile.gif";
height="20" width="20" alt="" border="0"></li><li>to preserve ordering across a
JMS queue consider using <a shape="rect" class="external-link"
href="http://activemq.apache.org/exclusive-consumer.html";>Exclusive
Consumers</a> in the <a shape="rect" href="activemq.html"
title="ActiveMQ">ActiveMQ</a> component</li><li>even better are <a shape="rect"
class="external-link"
href="http://activemq.apache.org/message-groups.html";>Message Groups</a> which
allows you to preserve ordering across messages while still offering
parallelisation via the <b>JMSXGroupID</b> header to determine what can be
parallelized</li><li>if you receive messages out of order you could use the <a
shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to put
them back together again</li></ul>
<p>A good rule of thumb to help reduce ordering problems is to make sure each
single can be processed as an atomic unit in parallel (either without
concurrency issues or using say, database locking); or if it can't, use a <a
shape="rect" class="external-link"
href="http://activemq.apache.org/message-groups.html";>Message Group</a> to
relate the messages together which need to be processed in order by a single
thread.</p>
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified:
websites/production/camel/content/parallel-processing-and-ordering.html
==============================================================================
--- websites/production/camel/content/parallel-processing-and-ordering.html
(original)
+++ websites/production/camel/content/parallel-processing-and-ordering.html Tue
Oct 9 14:19:21 2012
@@ -104,7 +104,7 @@
<p>This topic is large and diverse with lots of different requirements; but
from a high level here are our recommendations on parallel processing, ordering
and concurrency</p>
-<ul><li>for distributed locking, use a database by default, they are very good
at it <img align="middle" class="emoticon"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/smile.gif";
height="20" width="20" alt="" border="0"></li><li>to preserve ordering across a
JMS queue consider using <a shape="rect" class="external-link"
href="http://activemq.apache.org/exclusive-consumer.html";>Exclusive
Consumers</a> in the <a shape="rect" href="activemq.html"
title="ActiveMQ">ActiveMQ</a> component</li><li>even better are <a shape="rect"
class="external-link"
href="http://activemq.apache.org/message-groups.html";>Message Groups</a> which
allows you to preserve ordering across messages while still offering
parallelisation via the <b>JMSXGrouopID</b> header to determine what can be
parallelized</li><li>if you receive messages out of order you could use the <a
shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to put
them back together again</li></ul>
+<ul><li>for distributed locking, use a database by default, they are very good
at it <img align="middle" class="emoticon"
src="https://cwiki.apache.org/confluence/images/icons/emoticons/smile.gif";
height="20" width="20" alt="" border="0"></li><li>to preserve ordering across a
JMS queue consider using <a shape="rect" class="external-link"
href="http://activemq.apache.org/exclusive-consumer.html";>Exclusive
Consumers</a> in the <a shape="rect" href="activemq.html"
title="ActiveMQ">ActiveMQ</a> component</li><li>even better are <a shape="rect"
class="external-link"
href="http://activemq.apache.org/message-groups.html";>Message Groups</a> which
allows you to preserve ordering across messages while still offering
parallelisation via the <b>JMSXGroupID</b> header to determine what can be
parallelized</li><li>if you receive messages out of order you could use the <a
shape="rect" href="resequencer.html" title="Resequencer">Resequencer</a> to put
them back together again</li></ul>
<p>A good rule of thumb to help reduce ordering problems is to make sure each
single can be processed as an atomic unit in parallel (either without
concurrency issues or using say, database locking); or if it can't, use a <a
shape="rect" class="external-link"
href="http://activemq.apache.org/message-groups.html";>Message Group</a> to
relate the messages together which need to be processed in order by a single
thread.</p>
![https://cwiki.apache.org/confluence/images/icons/emoticons/smile.gif"](https://cwiki.apache.org/confluence/images/icons/emoticons/smile.gif"){kind=link}