| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| No MRM message body in trace file |
« View previous topic :: View next topic » |
| Author |
Message
|
| weihong |
 Posted: Thu Oct 09, 2003 7:57 pm Post subject: No MRM message body in trace file |
 |
|
Newbie
Joined: 08 Apr 2002
Posts: 8
|
Hi everyone,
Hope some of you can give ideas on how I can get a clue about what happened to my message.
Basically, I have a message set define (TDS) and set up MQSI message flow which contains an input, trace and output nodes for testing. I wrote the Root tree in the trace file. However, I only see the message header MQMD, but no MRM message body. there is no exceptions and the original message is written the output queue.
here is the trace file:
Exception List:
-----------------------------------------------------------------------
Root: (
(0x1000000)Properties = (
(0x3000000)MessageSet = 'DSR7EAC0PU001'
(0x3000000)MessageType = 'CUST830SNF_MSG'
(0x3000000)MessageFormat = 'TDS'
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Transactional = TRUE
(0x3000000)Persistence = FALSE
(0x3000000)CreationTime = GMTTIMESTAMP '2003-10-10 02:48:15.290'
(0x3000000)ExpirationTime = -1
(0x3000000)Priority = 0
(0x3000000)ReplyIdentifier = X'000000000000000000000000000000000000000000000
000'
(0x3000000)ReplyProtocol = 'MQ'
(0x3000000)Topic = NULL
)
(0x1000000)MQMD = (
(0x3000000)SourceQueue = 'TDS.TEST1.IN'
(0x3000000)Transactional = TRUE
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Format = ' '
(0x3000000)Version = 2
(0x3000000)Report = 0
(0x3000000)MsgType = 8
(0x3000000)Expiry = -1
(0x3000000)Feedback = 0
(0x3000000)Priority = 0
(0x3000000)Persistence = 0
(0x3000000)MsgId = X'414d51204d51443031514431202020203f84bcd0000b
d172'
(0x3000000)CorrelId = X'00000000000000000000000000000000000000000000
0000'
(0x3000000)BackoutCount = 0
(0x3000000)ReplyToQ = '
'
(0x3000000)ReplyToQMgr = 'MQD01QD1
'
(0x3000000)UserIdentifier = 'mqsi '
(0x3000000)AccountingToken = X'16010515000000b4b7cd221ed19818828ba628eb0300
0000000000000000000b'
(0x3000000)ApplIdentityData = ' '
(0x3000000)PutApplType = 11
(0x3000000)PutApplName = 'C:\RFHUtil\rfhutilc.exe'
(0x3000000)PutDate = DATE '2003-10-10'
(0x3000000)PutTime = GMTTIME '02:48:15.290'
(0x3000000)ApplOriginData = ' '
(0x3000000)GroupId = X'00000000000000000000000000000000000000000000
0000'
(0x3000000)MsgSeqNumber = 1
(0x3000000)Offset = 0
(0x3000000)MsgFlags = 0
(0x3000000)OriginalLength = -1
)
(0x1000021)MRM = (
why MRM = nothing?
Any ideas are appreciated. |
|
| Back to top |
|
 |
| skn |
| Posted: Fri Oct 10, 2003 5:47 am Post subject: |
|
|
Centurion
Joined: 21 May 2003
Posts: 112
Location: Dallas
|
| Since you seem to be doing nothing with the message , no exceptions might be generated even if the input is not in the correct format.Try inserting a compute node between input and trace node and try to change the value of any one element(i am sure wont be able to do that). |
|
| Back to top |
|
|
| EddieA |
| Posted: Fri Oct 10, 2003 7:50 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Take a look in the error log. I think you'll find that when the Trace node tried to parse your message, it failed.
You don't need to manipulate the message in a Compute. The Trace forces a parse.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| weihong |
| Posted: Fri Oct 10, 2003 7:12 pm Post subject: Thanks for the reply |
|
|
Newbie
Joined: 08 Apr 2002
Posts: 8
|
Thanks, guys.
The error was found in the unix syslog. it is a parsing error because the data was not valid.
Eddie, I am not clear why the error goes to the syslog, not the ExceptionList? in other words, what type of errors go to the syslog and what can be captured in the ExceptionList, which is easier for programmer
to look at? |
|
| Back to top |
|
|
| HugoB |
| Posted: Tue Oct 14, 2003 12:36 am Post subject: |
|
|
Acolyte
Joined: 26 Jun 2001
Posts: 67
|
You should enable a debug log, this you can do in the operations tab.
This will generate the log you need. Which might for a big part be the same as the syslog, but i have my doubts.
Read in the manual about logging, it's a bit tricky to read the log.
But it will give you the info you need about the parsing error in most cases. But debugging WMQI is still rather  |
|
| 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
|
|
|
|
