Fault handling allows a SOA suite component to handle error situations caused by outside web services. The error situations can be both business (e.g. invalid data value) and runtime faults (service unavailable). I’m aiming to handle business fault as much as possible in the composite (catch) while handle runtime faults outside the composite.
In the remaining of this blog I will describe an implementation of the Fault Management Framework to handle runtime faults.
I have implemented the following policy:
1) RemoteFault (invocation of a service fails)
- Start a retry cycle
standaard retryCount: 5
standaard retryInterval: 300 (seconden)
standaard exponentialBackoff: 2
Retry will take place after 5, 10, 20, 40 en 80 minutes.
- If it still fails, start a human intervention
2) All other unhandled (runtime) faults
- Start a human intervention