Author: buildbot
Date: Sun May 22 11:18:55 2016
New Revision: 988878
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/hystrix-eip.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/hystrix-eip.html
==============================================================================
--- websites/production/camel/content/hystrix-eip.html (original)
+++ websites/production/camel/content/hystrix-eip.html Sun May 22 11:18:55 2016
@@ -115,7 +115,7 @@
<to uri="mock:result"/>
</route>
</camelContext>]]></script>
-</div></div><h3 id="HystrixEIP-onFallbackvsonFallbackViaNetwork">onFallback vs
onFallbackViaNetwork</h3><p>If you are using onFallback then that is intended
to be local processing only where you can do a message transformation or call a
bean or something as the fallback. If you need to call an external service over
the network then you should use onFallbackVisNetwork that processes that wraps
that processing in another HystrixCommand that runs in its own thread pool to
not saturn the first command using in the Hystrix EIP.</p><h3
id="HystrixEIP-ConfiguringHystrixExample">Configuring Hystrix
Example</h3><p>Hystrix has many options as listed in the table above. For
example to set a higher timeout to 5 seconds, and also let the circuit breaker
wait 10 seconds before attempting a request again when the state was tripped to
be open.</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+</div></div><h3 id="HystrixEIP-onFallbackvsonFallbackViaNetwork">onFallback vs
onFallbackViaNetwork</h3><p>If you are using onFallback then that is intended
to be local processing only where you can do a message transformation or call a
bean or something as the fallback. If you need to call an external service over
the network then you should use onFallbackViaNetwork that runs in another
indepedent HystrixCommand that uses its own thread pool to not exhaust the
first command.</p><h3 id="HystrixEIP-ConfiguringHystrixExample">Configuring
Hystrix Example</h3><p>Hystrix has many options as listed in the table above.
For example to set a higher timeout to 5 seconds, and also let the circuit
breaker wait 10 seconds before attempting a request again when the state was
tripped to be open.</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"><