| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error Propagation |
« View previous topic :: View next topic » |
| Author |
Message
|
| venuprsd |
 Posted: Mon Oct 25, 2010 9:20 pm Post subject: Error Propagation |
 |
|
Apprentice
Joined: 15 Aug 2010
Posts: 44
|
Hello Experts,
You might think it's a very silly question but i read in the Info center still have confusion.
In Message Broker when exception goes to catch terminal and failure terminal. I tried with some example like sending invalid xml messages like. plz clarify this
Thank you. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Oct 26, 2010 5:24 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Moved.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| BDS |
| Posted: Tue Nov 02, 2010 6:23 am Post subject: |
|
|
Newbie
Joined: 21 Oct 2010
Posts: 8
|
Hi venuprsd
When a error occurs in a msgflow, the msg is sent back upstream - if it hits anode with a cath terminal it will try to go this route if connected - ultimately hitting the MQ input node for instance. If the catch is not connected here, it will be fwd to the failure terminal.
I think there is an error sample provided.
Try another simple example - alter the MQOutput node queue depth to 1 and watch the process in user trace or debug if you send more msgs in. |
|
| 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
|
|
|
|
