| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error handler design questions |
« View previous topic :: View next topic » |
| Author |
Message
|
| PGoodhart |
 Posted: Tue Jan 11, 2005 12:52 pm Post subject: Error handler design questions |
 |
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
Hi everyone,
I have a few "tactical" questions that I hope someone will have some input on.
My managment has come to the conclusion that error handling should be standardized for broker flows.
We run V5 currently.
I have a simple error "capture" subflow running now that dumps the exception tree to a message on a flow error.
Obviously the information to handle the error we need is in the exception tree so I figure I ought to just standardize on the exception tree structure as the "error" report structure. Does that make sense? The only thing I see is that it may contain more information then necessary.
Second question, there is some question whether this error information should be in a seperate message, or in a custom header. Is there any advantage/disadvatage to doing this one way or another?
Thanks!
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
 |
| tillywern |
| Posted: Tue Jan 11, 2005 2:46 pm Post subject: A bit or two on error handling. |
|
|
Centurion
Joined: 28 Jan 2003
Posts: 109
Location: Colorado
|
Methods for error handling are varied depending on situation. Having implemented/designed several there is not one way that is best. However consider the following;
1. Where do the messages go and how are they stored
2. How will they be reported on
3. Who will read them.
4. How much information really needs to be in them?
Several solutions present themselves quickly; store them in a database or in a file. Build a new error reporting infrastructure or use and existing one.
Build your generic error flow. Ensure that no matter what the primary means for reporting of errors, database, queue, etc., that if it fails the information can get written to a file. If your regular file system is provided over a network, you may want to have a place on a local file system to ensure that in the event of a bad failure that data has the best chance possible to get logged.
The error tree is good but is really not great in a support role. It tends to get to verbose too fast. Many times you will want to write the message that failed along with the reason for failure to the log, database, or queue. So wrap it and ensure you can recreate the MQMD if it is important.
Perhaps your error flow can dump the error tree to one file and the message and short error description to another. That way you don’t have to suffer through the error tree to view the data.
Be careful if you use a database to hold error messages. XA transactions get really funky and committing an error message to an error database table is considered successful transaction processing. It can cause interesting issues with flow coding and commit boundaries.
Never neglect the use of a trace node that puts a message to SDTERR or SYSLOG. Many monitoring tools automatically trigger on events sent to the SYSLOG. It can be a quick and dirty way to get your support software integrated into your flows.
Hope this gives you a start. |
|
| Back to top |
|
|
| javaforvivek |
| Posted: Wed Jan 12, 2005 2:26 am Post subject: |
|
|
Master
Joined: 14 Jun 2002
Posts: 282
Location: Pune,India
|
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jan 12, 2005 9:31 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
If you have access to Xephon's MQUpdate, you will find some articles realted to Error Handling.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| 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
|
|
|
|
