A short introduction on error handling in anypoint studio
- 1. A Short Introduction on Error Handing in Anypoint Platform By – Swapnil Sahu
- 2. Error Handling in Mule Mule provides numerous options for handling errors. Faults that occur within Mule are referred to as exceptions; when an activity in your Mule instance fails, Mule throws an exception. To manage these exceptions, Mule allows you to configure exception strategies.
- 3. Types of Exceptions From a high level perspective, errors that occur in Mule fall into one of two categories: • System Exceptions • Messaging Exceptions.
- 4. System Exceptions Mule invokes a System Exception Strategy when an exception is thrown at the system- level (i.e., when no message is involved, exceptions are handled by system exception strategies). When a system exception strategy occurs, Mule sends an exception notification to registered listeners, logs the exception, and if the exception was caused by a connection failure executes the reconnection strategy. System Exception Strategies are not configurable in Mule.
- 5. Messaging Exceptions Mule invokes a Messaging Exception Strategy whenever an exception is thrown within a flow (i.e., whenever a message is involved, exceptions are handled by messaging exception strategies). When a message being processed through a Mule flow throws an exception, normal flow execution stops and processes transfers to the message processor sequence within the exception strategy. You can incorporate any number of message processors and in one case, other exception strategies into an exception strategy to handle the exception precisely as you wish
- 6. Types of Exception Strategies
- 7. Characteristics of Messaging Exception Strategies • Each flow can contain only one exception strategy. However this can be a choice exception strategy that then refers to other nested exception strategies. • Choice exception strategies can contain one or more catch and/or rollback exception strategies. (Rollback and catch exception strategies cannot, however, contain other exception strategies.) • Each exception strategy can contain any number of message processors. • The exception strategy message processors should not throw exceptions, because you cannot create a nested exception strategy for these message processors.
- 8. Thank You