| Author |
Message
|
| chris boehnke |
 Posted: Sun Jul 01, 2007 5:59 pm Post subject: broker logs are filling so fast with exception error |
 |
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi all,
I am using the request and reply message flows and calling the web services by using http nodes.
My flows looks like this:
Request flow...MQInput->AggregateControl->Compute->MQOutput->Aggregate Request
Reply flow....MQInput->AggregateReply->Compute->MQReply
1. I created request and reply flows for Project 1(message flow project1 + messageset project 1) and the flow is working fine and getting the reply back.
2. I created another project called Project2(message flow project2 + messageset project 2) which is similar to Project 1. In this project we are using new message and another messageset created with a new cobol copybook compared to the project1. In this project 2 also I am getting the response back and working fine.
Now the problem is my broker logs are showing an error for the project 1.
Both projects are working fine and getting the response back but why the broker is throwing the errors in the broker logs. My broker logs are filling too fast.
The log shows below information:
An error occurred in parser
'Root' whilst parsing the field named 'XMLNS' on behalf of node 'SOASchema.FanInMF.AggReply - SVC_AGG'. Th
e data being parsed was '4d442020020000000000000002000000ffffffff0000000022020000b80400004d514852463220200300000000000000414d
51204d514d494d53473032424b31b3bd714686160020414d51204d514d494d53473032424b31b3bd7146047d0220000000002020202020202020202020202
020202020202020202020202020202020202020202020202020202020202020202020204d514d494d53473032424b31202020202020202020202020202020
2020202020202020202020202020202020202020206d716d20202020202020202000000000000000000000000000000000000000000000000000000000000
0000020202020202020202020202020202020202020202020202020202020202020201a0000004d514d494d53473032424b31202020202020202020202020
202020203230303730363231313934343234373120202020000000000000000000000000000000000000000000000000010000000000000000000000fffff
fff52464820020000004c0300002
Jul 1 21:38:58 WebSphere Broker v6002[24632]: (EG:test)[1230740400]BIP5009E: XML Parsing Errors have occurred. : BK1.df2d9084-1301-0000-0080-e788c081d139: /build/S600_P/src/MTI/MTIforBroker/GenXmlParser2/XmlImbParser.cpp
: 604: XmlImbParser::parseLastChild: :
Jul 1 21:38:58 WebSphere Broker v6002[24632]: (EG.test)[1230740400]BIP5004E: XML parsing error (The input ended before all started tags were ended. Last tag started was 'FIELD1' ) encountered on line 1 column 3373 while parsing element FIELD1. : BK1.df2d9084-1301-0000-0080-e788c081d139: /build/S600_P/src/MTI/MTIforBroker/
In the above logs FIELD1 belongs to Project2 FanIn message flow.
My broker logs are filling so soon as every minute broker is throwing the parsing error even there is no message sent.
Please help me out.
Thanks. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sun Jul 01, 2007 6:15 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you stop the broker, are there any messages sitting on queues?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Sun Jul 01, 2007 6:26 pm Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
| jefflowrey wrote: |
| If you stop the broker, are there any messages sitting on queues? |
Hi Jeff,
I stopped the broker and refreshed all the queues. I dont see any messages sitting on the queues.
Please suggest.
Thanks. |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Sun Jul 01, 2007 7:21 pm Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi Jeff,
I stopped the broker and refreshed all the queues. I dont see any messages sitting on the queues.
Please suggest.
Thanks.[/quote]
For the Project1, I used the these terms for the aggregate nodes:
Aggregate control ...AGG1
Aggregate request...AGGREQ1
Aggregate request(Original message)...ORIG_MSG1
For the Project2 these are the terms I used:
Aggregate control ...AGG2
Aggregate request...AGGREQ2
Aggregate request(Original message)...ORIG_MSG2
Please suggest me..
Thanks in advance. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jul 01, 2007 8:09 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Looks to me like you could gain some insight in checking out the aggregation model in the samples....
Anyways the output of the aggregation fan in node needs to be worked on in a compute node (or JCN) before it can be used as a decent standard XML message. Look up the documentation for the makeup of the output of the aggregation fan in node and how it presents the information in the different folders.... A trace right after the fan in node should help you understand a lot.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
