| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| why msg with unmatched format don't go the failure terminal? |
« View previous topic :: View next topic » |
| Author |
Message
|
| pcelari |
 Posted: Wed Feb 29, 2012 1:47 pm Post subject: why msg with unmatched format don't go the failure terminal? |
 |
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
In a MQInput node, I enabled validation and connected the failure terminal to an error logging and reporting subflow, which is intended to record and report both the message body and exceptionlist tree.
But when I put an invalid message, it first goes directly downstream despite the input portion contains "A parser Error has occurred".
Why does it behave this way? What would I have missed?
Beside, is there a way to record the original input message as a blob in case it cannot be parsed by the specified parser?
thanks for any insight!
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Feb 29, 2012 2:04 pm Post subject: Re: why msg with unmatched format don't go the failure termi |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| pcelari wrote: |
In a MQInput node, I enabled validation and connected the failure terminal to an error logging and reporting subflow, which is intended to record and report both the message body and exceptionlist tree.
But when I put an invalid message, it first goes directly downstream despite the input portion contains "A parser Error has occurred".
Why does it behave this way? What would I have missed?
Beside, is there a way to record the original input message as a blob in case it cannot be parsed by the specified parser?
thanks for any insight!
|
What's the timing on your parsing, immediate or on demand? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| pcelari |
| Posted: Wed Feb 29, 2012 2:41 pm Post subject: |
|
|
Chevalier
Joined: 31 Mar 2006
Posts: 411
Location: New York
|
it's the default 'On Demand'.
Now I seems to see it a little more. So if 'On Demand' is used, there is no need to connect the Failure terminal?
_________________
pcelari
-----------------------------------------
- a master of always being a newbie |
|
| Back to top |
|
|
| nandu123 |
| Posted: Wed Feb 29, 2012 3:40 pm Post subject: |
|
|
Newbie
Joined: 10 Jan 2011
Posts: 5
Location: NewYork
|
Quote from info center, hope this helps.
| Quote: |
| On Demand causes partial parsing to occur. When fields in the message are referenced, as much of the message is parsed as is necessary to completely resolve the reference. Therefore, fields might not be parsed until late in the message flow, or never. This restriction applies to both the message body and the message headers. |
| Quote: |
| Immediate and Complete both override partial parsing and parse the entire message, including any message headers |
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Mar 01, 2012 10:31 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| pcelari wrote: |
it's the default 'On Demand'.
Now I seems to see it a little more. So if 'On Demand' is used, there is no need to connect the Failure terminal?
|
No it just means that the offending part of the message may never be accessed and as such you would never see the error if validation is set to full
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
