Author: buildbot Date: Wed Jun 6 09:18:20 2012 New Revision: 820444 Log: Production update by buildbot for camel
Modified: websites/production/camel/content/cache/main.pageCache websites/production/camel/content/threading-model.html Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/camel/content/threading-model.html ============================================================================== --- websites/production/camel/content/threading-model.html (original) +++ websites/production/camel/content/threading-model.html Wed Jun 6 09:18:20 2012 @@ -94,7 +94,7 @@ </pre> </div></div> -<p>What that means is that for example when you use <a shape="rect" href="multicast.html" title="Multicast">Multicast</a> with <tt>parallelProcessing=true</tt> enabled, then it would create a thread pool based on the profile above. The <tt>rejectedPolicy</tt> have four options: <tt>Abort, CallerRuns, Discard, DiscardOldest</tt> which corresponds to the same four options provided out of the box in the JDK. </p> +<p>What that means is that for example when you use <a shape="rect" href="multicast.html" title="Multicast">Multicast</a> with <tt>parallelProcessing=true</tt> enabled, then it would create a thread pool based on the profile above. The <tt>rejectedPolicy</tt> has four options: <tt>Abort, CallerRuns, Discard, DiscardOldest</tt> which corresponds to the same four options provided out of the box in the JDK. </p> <p>You can define as many thread pool profiles as you like. But there must only <b>one</b> default profile. A custom thread pool profile will inherit from the default profile. Which means that any option you do not explicit define will fallback and use the option from the default profile.</p>