| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Database Input node throwing odbc exception in message flow. |
« View previous topic :: View next topic » |
| Author |
Message
|
| pkdec |
 Posted: Fri Jun 10, 2016 5:51 am Post subject: Database Input node throwing odbc exception in message flow. |
 |
|
Acolyte
Joined: 12 Feb 2015
Posts: 66
Location: Canada, QC
|
Hello All,
I am using Database Input node as my first node to interact with database.
I am unable to see exception tree populated, if the trigger table name itself is wrong.
I took a trace and i see its giving me error while accessing trigger table.
Is it not possible to see these errors in exception tree of message flow.
Thanks |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Jun 13, 2016 4:22 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
In this case, the Mesasge Flow itself is never even reached. So nothing can be propagated.
And you really wouldn't want it to be, either. A configuration problem like this would propagate messages nearly constantly, and any error handling you had in your message flow would be flooded with messages.
The error occurs in the ODBC layer, and should be reported in the system log as a normal Broker Error Message.
If you don't see it there, then you should probably open a PMR.
But if it's nowhere else, it should be in the odbc log file.
_________________
chmod -R ugo-wx / |
|
| 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
|
|
|
|
