| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Finding Detail Info Or Root Cause Info About An IIB Error |
« View previous topic :: View next topic » |
| Author |
Message
|
| EricL |
 Posted: Fri Aug 17, 2018 7:27 am Post subject: Finding Detail Info Or Root Cause Info About An IIB Error |
 |
|
Centurion
Joined: 10 Oct 2014
Posts: 102
|
Hi,
When coding ESQL in IIB on Windows platform, I come across some error messages from within EventViewer, basic info can be retrieved from there, but sometimes more detailed info is needed, like there is error level message with Event ID: 2230, the general message is:
(LocalBrkr.IntegrationServer) Error detected whilst processing a message in node 'File_InputOutput.Email Output'.
The integration node detected an error whilst processing a message in node 'File_InputOutput.Email Output'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
....
When look at the error messages, either Friendly View nor XML View, doesn't provide enough info to help troubleshooting, when searching "Event ID: 2230" from IIB 10 Information Center, don't find much helpful info either.....
My question is: Where can find more helpful info to help troubleshotting current errors...
Thanks.... |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Aug 17, 2018 7:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
The IIB message tree is a nested structure, with the most general error (typically the 2230 you quote) as the parent, with increasingly more detailed messages as recursive children of that. Usually 4 or 5 deep.
The EventViewer (as sane as any other Windoze application) tends to work from the inside out, showing the most detailed message first and ending with the most generic, which then shows up at the top of the list like it's the only error.
If all you're getting is the 2230 and there are no other messages at or about the same timestamp from IIB, speak to your Windows admin because something in the OS is filtering them out / redirecting them / turning them into firelighters / grating them up for the unicorns to eat.
Worst case (and I accept this is way non-optimal) write a subflow that recurses through the exception tree & writes the output to a file, turn that into a custom node and attach it to the left most Catch terminal.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| timber |
| Posted: Fri Aug 17, 2018 7:59 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
As you have already discovered, you cannot debug a message flow using Event Viewer or the syslog.
IIB has a message flow debugger for a reason. Use it for most problems that you encounter during development. If your problem requires more information than the debugger can give, you should get comfortable with taking and reading a user trace. |
|
| 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
|
|
|
|
