| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Failure Handling - Best Practices |
« View previous topic :: View next topic » |
| Author |
Message
|
| santy |
 Posted: Mon Sep 28, 2009 2:22 am Post subject: Failure Handling - Best Practices |
 |
|
Centurion
Joined: 03 Nov 2006
Posts: 141
|
Hi,
From where can I get the documentation of best practices on Failure Handling? Or How can we achive a good failure handling in case of normal message failures or in case of environmental problems through WMB 6.1? |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Sep 28, 2009 3:32 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
AFAIK, there is no official IBM docs/papers on this sometimes thorny subject.
Every site/system will have different requirements for error handling.
These can range from 'don't care as every message is guaranteed to be error free and no the database won't go down' to
Log everything multiple times and in the event of an error tell the world that something bad has gone wrong and if is a coding/design error then send an electric shock to the developer who coded it badly' (Ok, I'm joking about the last part)
There are no hard & fast rules for this.
That said, you might like to start with the following:-
- Code every flow to use a common error handling procedure
- Disable Automatic DB Errors causing an Exception (This may cause some discussion but it is the way I prefer) and manually check the status of every DB operation.
- In the error handling, package up the original message and the exception into a .zip file and email it to someone/everyone(not simple to do)
- Add code so that Tivoli, QPasa! etc can be used for error notification (if these tools are used in that environment)
I'm sure there are more.
It is very much a 'roll your own' thing.
For existing sites then you are pretty well bound to use their existing procedures. If you are working on a new site then you can possibly dictate the way things are done.
_________________
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. |
|
| Back to top |
|
|
| Luke |
| Posted: Mon Sep 28, 2009 4:31 am Post subject: |
|
|
Centurion
Joined: 10 Nov 2008
Posts: 128
Location: UK
|
There is a redbook called something like "bulletproofing message flows" which could be a good starting point for you. It's pre-V6.1, but I'd imagine most of it would still be applicable.
As smdavies says, there are lots of different approaches, which will be dictated by your requirements, monitoring software, personal preferences etc. |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Mon Sep 28, 2009 5:13 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
