| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| IBM Integration Bus V9 - Catch Unhandled Exceptions |
« View previous topic :: View next topic » |
| Author |
Message
|
| matws |
 Posted: Tue Apr 14, 2015 10:57 am Post subject: IBM Integration Bus V9 - Catch Unhandled Exceptions |
 |
|
Newbie
Joined: 14 Apr 2015
Posts: 1
|
Hi,
I am developing a framework containing a set of features which can (ideally) be apply to any architecture using IIB, with minimum changes to the existing architecture.
One of the requirements is to be able to catch any exceptions that have occurred on any flow, which have not been handled by the developer.
And I would also like to be able to do this without having to force the developer to perform any additional action (add a subflow, user-node, add monitoring events, ...).
In the windows version I am able to see all unhandled exceptions reaching the event viewer, so the events are being handle by the broker somehow.
I was wondering if there was a way to subscribe or intercept the event of an unhandled exception reaching the broker.
Thank you in advance,
Miguel |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Tue Apr 14, 2015 11:14 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I don't think that you can do what you want totally externally to the flow. Also does the the entry in the System Event log tell the whole story of the exception? It is usable in a production environment? Do you have access to the System event log on a minute by minute basis?
A good number of sites have a standard framework for all message flows.
These facilities are often enabled as sub-flows that the developers add to their flows.
These can take away responsibility for things like error handling, input and output auditing.
The one I currently use does things such as returning a properly constructed SOAP Fault message (for flows that use SOAP), returning a properly coded HTTP error message etc etc etc
These frameworks take a good deal of time and efffort to develop. Many are specifically tailored to the requirements of the site.
Once you have one then all the developer has to do is to add the subflows to their flow in the right place.
I am sure others will be along soon to add their $0.02 worth to the subject.
Finally,
do you really want every exception to his the system event log? Who is going to read them all? you could write them to a Database so the events are searchable etc etc etc.
Some of the failures in our system hit the Error Handler but do not cause an exception. These are non-fatal or controlled errors. A decent framwork will allow you to control this sort of stuff.
This whole area is quite complex and there is definitely more than one answer to the problem
_________________
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 |
|
|
| mqjeff |
| Posted: Tue Apr 14, 2015 11:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| akil |
| Posted: Wed Apr 15, 2015 7:49 pm Post subject: |
|
|
Partisan
Joined: 27 May 2014
Posts: 338
Location: Mumbai
|
I think the only way to catch un-handled exceptions is to attach a node to the catch terminal of the input node of the flow ..
What's usually attached to the catch terminal is a sub-flow, often packaged as a library , that does what-ever is deemed appropriate for the exceptions.
So I suppose the flows will have to be touched..
It might be possible to add these sub-flows via altering the message flow xml files via an ant script, but that kind of thing isn't officially supported..
_________________
Regards |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Apr 15, 2015 10:20 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| akil wrote: |
I think the only way to catch un-handled exceptions is to attach a node to the catch terminal of the input node of the flow ..
What's usually attached to the catch terminal is a sub-flow, often packaged as a library , that does what-ever is deemed appropriate for the exceptions.
So I suppose the flows will have to be touched..
It might be possible to add these sub-flows via altering the message flow xml files via an ant script, but that kind of thing isn't officially supported.. |
and what happens to all this exceptions that are generated during development?
I have to wonder if the OP is on a search for El Dorado?
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
