| Author |
Message
|
| Lisa |
 Posted: Fri Sep 21, 2007 11:51 am Post subject: XMLS Issue |
 |
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
All,
How can I resolve the following error? Here is my flow.
Input(BLOB) --> RCD (XML) --> Compute --> Output
Timestamps are formatted in local time, 240 minutes before GMT.
Trace written by version ; formatter version 6003
2007-09-21 15:42:23.170780 6683 UserTrace BIP4040I: The Execution Group ''default'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2007-09-21 15:42:23.171205 6683 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''MQSIDUT2''. The MQCC was '0' and the MQRC was '0'.
2007-09-21 15:42:23.171226 6683 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''MQSIDUT2''.
2007-09-21 15:42:33.563545 6683 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2007-09-21 15:42:33.563709 6683 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'.
2007-09-21 15:42:33.563770 6683 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.
2007-09-21 15:42:33.563911 6683 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '231' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
Threads enco |
|
| Back to top |
|
 |
| Bill.Matthews |
| Posted: Fri Sep 21, 2007 12:03 pm Post subject: |
|
|
Master
Joined: 23 Sep 2003
Posts: 232
Location: IBM (Retired)
|
The last entry is the trace is: (emphasis added)
2007-09-21 15:42:33.563911 6683 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '231' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
The parser name is incorrect - you have three choices for a generic XML parser - XML or XMLNS or XMLNSC
there is not a XMLS - so, to fix your problem, specify the correct parser name in the Reset Content Descriptor node.
_________________
Bill Matthews |
|
| Back to top |
|
|
| Lisa |
| Posted: Fri Sep 21, 2007 12:08 pm Post subject: XMLS Issue |
|
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
Hi Bill,
As stated in my first posting, I have the following things set in my message flow:
Input is set to BLOB and RCD is set to XML. I have tried setting these node values to XMLNS and XMLNSC. I think something is wrong with the input message, but I don't know what!
Input(BLOB) --> RCD (XML) --> Compute --> Output |
|
| Back to top |
|
|
| Bill.Matthews |
| Posted: Fri Sep 21, 2007 1:08 pm Post subject: |
|
|
Master
Joined: 23 Sep 2003
Posts: 232
Location: IBM (Retired)
|
From what you have shown in the trace - which appears to be a partial trace - i.e. it does not show anything past the msg flow being initialized - it is impossible to tell what the problem is.
Is there some reason that you have are using a RCD rather than specifying the pasring information in the MQInput node?
You have not stated the version/release/fix level for your Message Broker.
Since you can't attach a picture - please provide what is specified for the parser configuration for the MQInput node.
Did you use the pull-down to select the parser domain?
Please specify the configuration information and check boxes for the RCD node.
Insert two trace nodes in the msg flow - one just after the MQInput node and one after the RCD.
Provide any Application Entries in the Windows Even viewer that may be generated when the flow is run.
Verify that the input message is properly mormed XML - for example, can you open the sample input with IE or Firefox?
Do all of the above - and - if necessary post back.[/img]
_________________
Bill Matthews |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Sep 21, 2007 1:27 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Lisa : I don't see any error in that trace. I do see a perfectly standard set of messages relating to a deploy operation. The XMLS parser is an internal XML parser which is used only for parsing deploy messages, |
|
| Back to top |
|
|
| Lisa |
| Posted: Sun Sep 23, 2007 9:34 pm Post subject: XMLS |
|
|
Master
Joined: 07 Jun 2002
Posts: 287
Location: NJ
|
Thanks for the tips. I will review the message flow today and post the results.
Lisa |
|
| Back to top |
|
|
|
|
