Posted: Mon Oct 26, 2009 9:52 am Post subject: Common Error Handling Flow
Partisan
Joined: 24 Sep 2003 Posts: 355
We are planning to design our common middle-ware services, one of them being 'Error Handling SubFlow'. What are the typical features we would like incorporate?
1. Better manageability (failure messages to database rather than a queue
2. Notification (Email/pager etc.,)
3. Retry intervals for any system errors
4. Better visibility (Actual error message stripped out of message tree)
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
All of your points are certainly acheivable.
But...
What you implement really depends upon the business requirements.
I'd probably add the following to your list.
- Zip up the offending message (inc headers) so that it can be replayed on another system
- Control the operation of the error flow by values in a DB table (As opposed to a properties file)
I have a template error handling flow that I have used in several different places. Once you take the time to develop such a flow it can be used with very few modifications in other places. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum