| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Trace Node data appears to be truncated |
« View previous topic :: View next topic » |
| Author |
Message
|
| TonyD |
 Posted: Wed Jan 07, 2004 5:27 pm Post subject: Trace Node data appears to be truncated |
 |
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
I have flows that include several trace nodes with 'Destination=User Trace' and 'Pattern=${Root}'. The data being displayed is XML. I normally use usertrace.cmd to look at the trace output after testing a flow.
I have noticed that the Pattern output appears to be truncated, for example:
| Quote: |
(0x01000013)urn:oasis:names:tc:ciq:xsdschema:xCIL:2.0:IDCard = (
(0x0300000B):Type = 'Driver License'
(0x01000013)urn:oasis:names:tc:ciq:xsdschema:xCIL:2.0:Number = (
(0x020000' from trace node 'mfCIL.Trace'.
The trace node 'mfCIL.Trace' has output the specified trace data. |
I altered the Trace Node to write output to a file, and the complete data is now shown (continuation of above data shown....not the entire message):
| Quote: |
(0x01000013)urn:oasis:names:tc:ciq:xsdschema:xCIL:2.0:IDCard = (
(0x0300000B):Type = 'Driver License'
(0x01000013)urn:oasis:names:tc:ciq:xsdschema:xCIL:2.0:Number = (
(0x0200000D): = 'M1234567'
)
(0x01000013)urn:oasis:names:tc:ciq:xsdschema:xCIL:2.0:IDCardIssuePlace = (
(0x01000013)urn:oasis:names:tc:ciq:xsdschema:xAL:2.0:Country = (
(0x01000013)urn:oasis:names:tc:ciq:xsdschema:xAL:2.0:CountryName = (
(0x0200000D): = 'India'
|
I have used trace nodes many times but have not previously noticed that data is missing. I also tested with mqsireadlog/mqsiformatlog and got the same truncation. I am using WBIMB V5 CSD2. I am not aware of any parameter that specifies the maximum length of 'pattern' output if directed to the UserTrace option but it appears that there may be some limitation. Any suggestions? |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Jan 07, 2004 6:24 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
What is happening to your message? IS it going to the output queue? I believe there is some kind of parsing error occuring in your message flow, so the message is rolled-back. Since you have ${Root} in your trace node, WMQI will try to parse the message, if your input XML is not well-formed, it will throw an exception.
You can add try-catch nodes in your message flow and try to capture the ExceptionList, which will give you more info about the problem.
_________________
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 |
|
|
| TonyD |
| Posted: Thu Jan 08, 2004 1:59 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
| The message goes to the output queue, in both cases (inline Trace output and to file). Furthermore the output message is complete...no truncation. In my test I simply have an MQInput, a Trace and an MQOutput node as I am testing validation of the messages against reasonably complex XML schemas. There are no validation errors. The truncation occurs with different input messages.... one is 9K, another is 34K. Will experiment further! |
|
| 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
|
|
|
|
