| Author |
Message
|
| ivanachukapawn |
 Posted: Fri Jan 05, 2007 7:08 am Post subject: Mapping Node failure and Trace Node problem |
 |
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
I'm using a mapping node configured to a map which simply maps XML elements from the input message to XML elements in the output message. The elements are named the same in both messages and they have the same type.
For whatever reason (which I'm trying to determine) the message propogates through the failure terminal of the mapping node.
The failure terminal is wired to a Trace Node. I specified user trace and configured to ${root}
I look at the trace.log via mqsiformatlog
I'm expecting to see a screwed up message but instead the following three error messages are displayed as output from mqsiformatlog
'
Timestamps are formatted in local time, 300 minutes before GMT.
BIP5004E: XML parsing error ('Invalid document structure ') encountered on line 1 column 1 while parsing element ''
and
BIP8047E: Unable to parse the data received, etc. etc. etc.
What do you suppose is happening here? |
|
| Back to top |
|
 |
| ivanachukapawn |
| Posted: Fri Jan 05, 2007 7:30 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
UPDATE: I discovered that my map had a problem in that I was not mapping the properties from input message to output message.
When I fixed that problem, the mapping node propogated my message through the out terminal.
I have the out terminal wired to a trace node also and the trace node propogates through its out terminal to an MQOutput node.
I do have a message on my output queue and it looks OK to me.
However, when I run mqsiformatlog -i <log file from trace node wired to mapping node out terminal> - I see the same 3 messages that I described in my original post.
I guess I'm just not using the Trace Node correctly.
ivana |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 05, 2007 7:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You always have to manually clean out trace files.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Fri Jan 05, 2007 7:37 am Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
OK I'll clean out the trace.log before running each time.
But shouldn't I see the message by virtue of configuring the trace node with ${root} ? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jan 05, 2007 7:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
not if the message failed to parse...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jan 06, 2007 11:57 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I do not bother to format the trace log.
As I have messages that are CWF this would not be practical, especially when there are errors: (${root}, ${ExceptionList}...) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
