| Author |
Message
|
| prasadpav |
 Posted: Tue Nov 28, 2006 5:22 am Post subject: MQGET Failure terminal acting as a Catch terminal |
 |
|
Centurion
Joined: 03 Oct 2004
Posts: 142
|
Hi,
I'm using MB v6 and I haven't applied any fix packs yet. I'm seeing this strange behaviour while using MQGET nodes. If there is any exception down the message flow after MQGET, the exception is propagated to the failure terminal of the MQGET and not to the MQINUT catch terminal. To prove it, this is what I did:
| Quote: |
MQGET (failure) ->Trace2
MQINPUT(out) -> MQGET (out) -> throw
MQINPUT(catch) ->Trace1
|
When I use this, I get output from "Trace2" and not "Trace1".
Is this behaviour correct?? sounds wrong to me...
Regards,
Prasad |
|
| Back to top |
|
 |
| kspranava |
| Posted: Wed Nov 29, 2006 1:00 am Post subject: |
|
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Hi prasadpav,
This behaviour is perfectly right. If you want the exception to be routed to input node don't wire any of the failure terminals of nodes other than input node.
-kspranava. |
|
| Back to top |
|
|
| mgk |
| Posted: Wed Nov 29, 2006 1:44 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
No, I believe this behaviour to be wrong! Only Failures (exceptions) that happen within a node should be sent to that nodes failure terminal. Once a message has been propagated to a terminal, then any exceptions that happen downstream in other nodes should not be caught by the first (propagating) node, they should only be caught by a node with a wired catch terminal (if any) e.g. an input node or a catch node.
I think you need to raise a PMR to get a fix for this.
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| kspranava |
| Posted: Wed Nov 29, 2006 2:56 am Post subject: |
|
|
Centurion
Joined: 27 Apr 2003
Posts: 124
|
Hi,
Sorry, for misleading... confused between catch and failure terminals.
mgk, thanks for pointing it out rightly.
-kspranava. |
|
| Back to top |
|
|
| jharringa |
| Posted: Wed Nov 28, 2007 3:52 pm Post subject: |
|
|
Acolyte
Joined: 24 Aug 2007
Posts: 70
|
Has anyone had any luck finding a resolution for this? I am experiencing the same issue.
I posted before I could find this message (after going through a bunch of different searches): http://www.mqseries.net/phpBB2/viewtopic.php?t=40794
It appears that this is addressed in FixPack 6.0.0.6 (which I didn't know was available). It still may be preferrable to work around this in the short term. |
|
| Back to top |
|
|
| EddieA |
| Posted: Thu Nov 29, 2007 9:55 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
You might try with FixPack 5, or 6. There was an issue relating to any node written in Java "catching" an upstream error, in error, that was fixed in 5.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
