| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| varying length copybook message |
« View previous topic :: View next topic » |
| Author |
Message
|
| LazyBoy |
 Posted: Tue Jul 14, 2009 5:18 am Post subject: |
 |
|
Voyager
Joined: 04 May 2006
Posts: 78
|
Hi Kimbert,
I double checked the trace level, it is at debug level.
C:\WMB\TOOLS\WMB610_Runtime>mqsireporttrace WBRK61BROKER -u -e default
BIP8098I: Trace level: debug, mode: safe, size: 4096 KB.
lets permute and combine the different solutions for this error.
Please suggest me.
Thanks. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Jul 14, 2009 7:49 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Increase the size of your trace log. It's probably wrapping, and throwing away the interesting bits. I always set it to at least 50Mb. |
|
| Back to top |
|
|
| LazyBoy |
| Posted: Wed Jul 15, 2009 12:38 pm Post subject: |
|
|
Voyager
Joined: 04 May 2006
Posts: 78
|
Hi Kimbert,
I did increase the file size to 50 MB, But I still dont see any change in the trace file generated.
Here is the exception message generated:
| Code: |
The MQ Get node 'MYFLOWService.MYQUEUE1' failed to navigate to the default location ''InputLocalEnvironment.MQ.GET'' for ''Input MQ Parameters Location''.
Location ''InputLocalEnvironment.MQ.GET'' is the default value for ''Input MQ Parameters Location'' and it was not found. It is assumed that this ''Input MQ Parameters Location'' node property is not needed in this case and, therefore, the issue is ignored.
Ignore this message (and the previous user trace message regarding this navigation, if there is one) if this ''Input MQ Parameters Location'' node property is not needed; Otherwise, make sure the location is available or correct the location specification.
2009-07-14 16:53:56.939968 5508 UserTrace BIP2657I: MQGetNode 'MYFLOWService.MYQUEUE1' has completed its MQGET() call. The returned MQ codes are: MQCC=0, MQRC=0.
MQGetNode 'MYFLOWService.MYQUEUE1' has made 1 attempt(s) at calling MQGET() to read queue ''MYQUEUE'' of queue manager ''WBRK61QMGR''. The last call returned with MQ completion code 0 and reason code 0.
If the call(s) failed (returned with a non-zero return code), check the error codes and the other information provided to determine the cause of the failure and take any action necessary to resolve the problem. Possible causes include incorrect queue name, queue not readable, and message too large.
2009-07-14 16:53:56.939968 5508 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'MQAGENCY.REGUPDATE_PINITIAL.SOAP Input' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2009-07-14 16:53:56.939968 5508 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'MQAGENCY.REGUPDATE_PINITIAL.SOAP Input' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2009-07-14 16:53:56.939968 5508 UserTrace BIP6061I: Parser type ''MRM'' created on behalf of node 'MQAGENCY.REGUPDATE_PINITIAL.SOAP Input' to handle portion of incoming message of length '529' bytes beginning at offset '364'. Parser type selected based on value ''MRM'' from previous parser.
2009-07-14 16:53:56.939968 5508 UserTrace BIP2658I: MQGetNode 'MYFLOWService.MYQUEUE1' is propagating a message to the 'Output' Terminal.
None
None
2009-07-14 16:53:56.940311 5508 UserTrace BIP2539I: Node 'MYFLOWService.Trace': Evaluating expression ''Root'' at ('', '1.3'). This resolved to ''Root''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2009-07-14 16:53:58.191059 5508 Error BIP2628E: Exception condition detected on input node 'MQAGENCY.REGUPDATE_PINITIAL.SOAP Input'.
The input node 'MQAGENCY.REGUPDATE_PINITIAL.SOAP Input' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2009-07-14 16:53:58.191059 5508 RecoverableException BIP2230E: Error detected whilst processing a message in node 'MYFLOWService.Mapping.ComIbmCompute'.
The message broker detected an error whilst processing a message in node 'MYFLOWService.Mapping.ComIbmCompute'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2009-07-14 16:53:58.191059 5508 RecoverableException BIP2488E: ('gen.MQAGENCY.IBM_WBIMB_M_REVERSEFLOW_MQAGENCYService_REGUPDATE_PINITIAL_Mapping.MAIN', '3.1') Error detected whilst executing the SQL statement ''gen.MQAGENCY.M_REVERSEFLOW_MQAGENCYService_REGUPDATE_PINITIAL_Mapping(InputRoot, OutputRoot, InputLocalEnvironment, OutputLocalEnvironment);''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error.
2009-07-14 16:53:58.191059 5508 RecoverableException BIP2934E: Error detected whilst executing the function or procedure ''M_REVERSEFLOW_MQAGENCYService_REGUPDATE_PINITIAL_Mapping''.
The message broker detected an error whilst executing the function or procedure ''M_REVERSEFLOW_MQAGENCYService_REGUPDATE_PINITIAL_Mapping''. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2009-07-14 16:53:58.191059 5508 RecoverableException BIP2488E: ('gen.MQAGENCY.M_REVERSEFLOW_MQAGENCYService_REGUPDATE_PINITIAL_Mapping', '762.2') Error detected whilst executing the SQL statement ''PROPAGATE FINALIZE DEFAULT DELETE DEFAULT;''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error.
2009-07-14 16:53:58.191059 5508 RecoverableException BIP2230E: Error detected whilst processing a message in node 'MYFLOWService.Trace'.
The message broker detected an error whilst processing a message in node 'MYFLOWService.Trace'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2009-07-14 16:53:58.191059 5508 ParserException BIP5285E: Parsing errors have occurred.
Message set name: 'M_P_INITIAL_CC'
Message format: 'Text1'
Message type path: '/msg_RESPD/DATE'
Review other error messages to find the cause of the errors.
2009-07-14 16:53:58.191059 5508 ParserException BIP5421S: Tagged/Delimited String Format (TDS) parsing error
Current message : ''msg_RESP''
Path to current element : ''/msg_RESP/TERM''
Offset from start of message : 529
See following errors for more details.
2009-07-14 16:53:58.191059 5508 ParserException BIP5426E: The bitstream of a TDS message contains less data than expected.
The TDS parser could not complete parsing because the bitstream contains less data than expected. This could be caused by either an incorrect value for the Length property in the message definition, or by an inconsistent value inside a LengthRef field.
Make sure that the incoming message is a consistent message under the TDS message definition.
2009-07-14 16:53:58.191059 5508 UserTrace BIP3724I: Node 'MQAGENCY.REGUPDATE_PINITIAL.SOAP Input' sending a SOAP fault message to the originating client.
See subsequent messages for success or failure messages relating to this reply, and for any transport-specific messages.
No action required.
2009-07-14 16:54:24.837095 5512 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2009-07-14 16:54:24.839502 5512 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2009-07-14 16:54:24.841617 5512 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2009-07-14 16:54:24.847402 5512 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '235' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
5372 5508 5512
|
|
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
