| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| generic error handler |
« View previous topic :: View next topic » |
| Author |
Message
|
| mbwannabe1 |
 Posted: Wed Apr 18, 2012 8:26 am Post subject: generic error handler |
 |
|
Novice
Joined: 18 Apr 2012
Posts: 13
|
| Hi All, I am trying to create a generic error handler subflow based on the errorhandler sample that comes with MB 7. I ve replaced the Database Insertion compute node and MQ output node with a simple trace node. However the errors I am getting are not very descriptive. Seeing that there are many posts on this topic, has there been any attempt made to come up with a generic error handler flow or subflow? thanks |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Apr 18, 2012 8:48 am Post subject: Re: generic error handler |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mbwannabe1 wrote: |
| Seeing that there are many posts on this topic, has there been any attempt made to come up with a generic error handler flow or subflow? thanks |
Yes, we've all written something generic that fits into our sites' standards. With varying levels of success as indicated by the number of posts.
The most generic part will be the code that walks the exception tree.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mbwannabe1 |
| Posted: Wed Apr 18, 2012 8:59 am Post subject: |
|
|
Novice
Joined: 18 Apr 2012
Posts: 13
|
| I adapted the sample to use a trace node to write out the exception tree to a file. is that ok to do? I tried testing it with a malformed XML but didnt get an error that indicated explicitly that it was an XML parsing error (which I would have got with trace) or the BIP messages from the catalog. could I be doing something wrong and is there a better way to do this? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 18, 2012 9:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mbwannabe1 wrote: |
| could I be doing something wrong and is there a better way to do this? |
You're certainly doing something wrong. All the errors and messages you see in the trace are in the exception tree.
Trace nodes are also not the best way of capturing the data. If you want the entire exception tree (or the edited highlights) in a single point, use the one of the output node (depending on your preference) to do this. If you want to produce a single line in a log file, use log4j from the support pac or directly from a JCN (depending on your preference).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| 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
|
|
|
|
