Error Handling In Mule 4 | MuleSoft Mysore Meetup #10
- 1. 1
- 2. November 12, 2022 Mysore MuleSoft Meetup Error Handling in Mule 4
- 3. Safe Harbour Statement ● Both the speaker and the host are organizing this meet-up in individual capacity only. We are not representing our companies here. ● This presentation is strictly for learning purposes only. Organizer/Presenter do not hold any responsibility that same solution will work for your business requirements. ● This presentation is not meant for any promotional activities. 3
- 4. A recording of this meetup will be uploaded to events page within 24 hours. Questions can be submitted/asked at any time in the Chat/Questions & Answers Tab. Make it more Interactive!!! Give us feedback! Rate this meetup session by filling feedback form at the end of the day. We Love Feedbacks!!! Its Bread & Butter for Meetup. Housekeeping 4
- 5. Introduction ● About the Organizers 5 Shubham Chaurasia Billennium India Professional Integration Developer A SHOW OF HANDS: Who is new to this Meetup? Giridhar Meka Sr. Technical Architect
- 6. Certified MuleSoft Developer 2+ years of Total Experience, 1.5+ years in MuleSoft Working as Software Engineer at HashedIn By Deloitte ● About the Speaker Speaker 6 Abhishek Goel Software Engineer
- 7. 7 ● Introduction ○ What are Errors & Error Types? ○ Components of a Mule Error ○ Creating Custom Errors ○ On-Error Components ○ Handling Errors at different levels ○ Performing different Actions with different Errors ● Demo ● Trivia ● Wrap-Up Agenda
- 8. In Mule, errors are a way of communicating that something went wrong and providing meaningful information so that a user can take corrective action depending on the kind of error that was thrown. Errors 8 Types of Mule Errors System Errors: Mule throws a system error when an exception occurs at the system level and no Mule event is involved. A system error handler manages exceptions that occur: 1. During application startup. 2. When a connection to an external system fails. Messaging Errors: Mule throws a messaging error (a Mule error) whenever a problem occurs within a flow of a Mule app, where Mule events and the messages they contain are processed.
- 9. Components of Mule Message Error 9
- 10. • Mule errors have a namespace and Identifier and they belong to a hierarchy of error types which enables distinguishing of errors. For ex: HTTP: NOT_FOUND, FILE:NOT_FOUND enables developer to identify which connector is throwing the error. • Error types can have a parent type. This hierarchy implies that each error type is a specification of more global error type. The hierarchies enable you to route errors in a general or more specific way. For ex: The parent of HTTP: UNAUTHORIZED is MULE:CLIENT_SECURITY and parent of MULE:CLIENT_SECURITY is MULE:SECURITY. • All errors that can be handled come under ANY. Error Hierarchy and Types 10
- 11. This is used to define namespaces that are related to the particular Mule app name or context and avoid using existing connector namespaces. Custom Errors are used to make error messages more informative. For ex: Mapping an error occurring in customer app can be mapped with Customer namespace and order app can be mapped with Order namespace. Custom Errors 11
- 12. Messaging errors can be handled mainly through 4 ways: 1. Default Error Handler: By default, unhandled messaging errors are logged and propagated. When a flow is processing a Mule message that raises an error, the normal execution of the flow stops, and the process transfers to the flow’s default error handler, which propagates the error. Handling Errors 12
- 13. Handling Errors 2. Global Level Error Handling: An Error Handler flow can be designed and referenced from other flows or try blocks. A reusable configuration can be made to define a general error handling technique of the application. For ex: If the application is supposed to notify the stakeholders as soon as an error scenario arises in the application, then a global error handler can be designed and referenced. 13
- 14. Handling Errors 3. Flow Level Error Handling: On error components (On Error Continue and On Error Propagate) can be used inside a built-in or external Error Handler component. Flow level error handling is preferred when you want to handle cases that are specific to the flow. 14 4. Component Level Error Handling: Components can be enclosed inside a try block which has an in-built error handler. This is generally used when the application is trying to connect with any external system or inside a sub-flow which does not have it’s own error handler.
- 15. 15 On-Errors Components On-Error components differ in the way they affect their owner, that is, the Flow or Try scope where they are defined. On-error Propagate: Executes but propagates the error to a higher level, such as a containing scope (for example, to a Flow that contains a Try scope where the error occurs) or external flow containing a Flow Reference to the flow in which an error occurs. The error breaks the owner’s execution and propagates to that higher level, causing a failure at that level. In addition, any transaction the owner handles is rolled back.
- 16. On-Error Continue: Executes and uses the result of the execution as the result of its owner, as if the owner completed the execution successfully. Any transaction the owner handles is committed. However, note that the transaction is not committed if another component (one that does not own On Error Continue) created the transaction. On Error Components 16
- 18. Demo
- 19. Q&A
- 20. Take a stand ! 20 ● Nominate yourself for the next meetup speaker and suggest a topic as well.
- 21. 21 ● Share: ○ Tweet using the hashtag #MuleSoftMeetups ○ Join Mysore Group: https://meetups.mulesoft.com/mysore/ ● Feedback: ○ Fill out the survey feedback and suggest topics for upcoming events ○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program ○ Reach out to Mysore Meetup Leaders (Shubham / Giridhar) to suggest topics for next Meetup What’s next?
- 22. Get ready to WIN a MuleSoft Voucher from MuleSoft Quiz Time
- 23. Thank you