Author |
Message
|
HOMETOWN47 |
Posted: Mon Sep 27, 2004 2:11 am Post subject: Invaid Characters in RecoverableException of Trace node |
|
|
Apprentice
Joined: 25 Mar 2003 Posts: 34
|
I've got a trace node wired up on the catch node of my input node and outputting the {ExceptionList}. When I retrieve this information I get the following :-
2004-09-27 10:20:28.393732 2057 UserTrace BIP4060I: Data '*** A1 Exception ***
(
(0x1000000)RecoverableException = (
(0x3000000)File = '0000' from trace node 'build/S210_P/src/DataFlowEngine/ImbMqOutputNode.cpp'
(0x3000000)Line = 715
(0x3000000)Function = '0000'.
The trace node 'build/S210_P/src/DataFlowEngine/ImbMqOutputNode.cpp'
(0x3000000)Line = 715
(0x3000000)Function = '0000' has output the specified trace data.
Any ideas why I get the weird characters in the File and Function fields ? These characters are then causing problems when I try and output the Exception list as an XML message. |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Sep 27, 2004 4:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
What are the contents of these properties on the Trace node in your flow? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
HOMETOWN47 |
Posted: Mon Sep 27, 2004 7:56 am Post subject: |
|
|
Apprentice
Joined: 25 Mar 2003 Posts: 34
|
What do you mean contents of these properties ?
Is that not what the trace that I've included in the original message showing ? Pleas explain yourself.... |
|
Back to top |
|
 |
kirani |
Posted: Mon Sep 27, 2004 10:29 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
Print ${Root.Properties} in your trace node and post the output here. Also what CSD level you are at? _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
HOMETOWN47 |
Posted: Tue Sep 28, 2004 3:57 am Post subject: |
|
|
Apprentice
Joined: 25 Mar 2003 Posts: 34
|
This is the trace for the ${Root.Properties}
2004-09-28 12:50:29.047416 2057 UserTrace BIP4060I: Data '*** After Notify ***
(
(0x3000000)MessageSet = ''
(0x3000000)MessageType = ''
(0x3000000)MessageFormat = 'XML'
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 850
(0x3000000)Transactional = TRUE
(0x3000000)Persistence = TRUE
(0x3000000)CreationTime = GMTTIMESTAMP '2004-09-28 11:50:27.060'
(0x3000000)ExpirationTime = -1
(0x3000000)Priority = 0
(0x3000000)ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
(0x3000000)ReplyProtocol = 'MQ'
(0x3000000)Topic = NULL
)
' from trace node 'UKG.ZAC.GENZ.Trace1'.
I've managed to work around the problem in that we output everthing to an XML message using :-
DECLARE MyCardinality INTEGER;
SET MyCardinality = CARDINALITY("InputRoot".*[]);
DECLARE MyIndex INTEGER;
SET MyIndex = 1;
WHILE MyIndex < MyCardinality DO
SET OutputRoot.XML."ERROR"."ZIP".*[MyIndex] = "InputRoot".*[MyIndex];
SET MyIndex = MyIndex + 1;
END WHILE;
--SET "OutputRoot"."XML"."ERROR"."ZIP"."HexBody" = BITSTREAM("InputBody");
SET "OutputRoot"."XML"."ERROR"."ZIP"."ExceptionList" = "InputExceptionList";
SET "OutputRoot"."XML"."ERROR"."ZIP"."DestinationList" = "InputDestinationList";
The problem is with viewing this XML message with the util we use, WatchQ, because it sees the dodgy characters and truncates the message. We also use an in-house VB app to retrieve the XML messages and view them using IE. This method works fine and ignores the characters. It would still be interesting to know why were getting the characters in the first place....
Oh yes, CSD is 5 (I think!) and were still using WMQ2.1 |
|
Back to top |
|
 |
|