MQSeries.net :: View topic

siri2083 · Posted: Fri Jul 17, 2009 1:51 am Post subject:

Hi,

i am using a complex message set of xml message foramt. My flow is looks like: MQInputNode------>COmputeNode----->MQOutputNode.

in the input node properties, i have set below properties:
Message Domain,Message set, Message Type, Message format and in parsing Options tab parse timing as 'immediate' and validation tab validate = 'Content and Value', failure action as 'Exception list'.

Now my Xsd for creating the messageset is:

<xsd:schema version="0.14" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="contract" type="ContractType" />
<xsd:complexType name="ContractType">
<xsd:sequence>
<xsd:element minOccurs="0" name="contractID" type="xsd:string" />
<xsd:element minOccurs="0" maxOccurs="unbounded" name="billingSummary" type="BillingSummaryType" />
</xsd:sequence>
</xsd:complexType>

<xsd:complexType name="BillingSummaryType">
<xsd:sequence>
<xsd:element minOccurs="0" name="billingSummaryID" type="xsd:string" />
<xsd:element minOccurs="0" name="paymentsRemaining" type="xsd:string" />
<xsd:element minOccurs="0" name="frequencyModeCode" type="xsd:string" />
<xsd:choice>
<xsd:element minOccurs="0" name="paymentSourceBankAccount" type="xsd:string" />
<xsd:element minOccurs="0" name="paymentSourceChargeCard" type="xsd:string" />
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

I want to check the validation of input message. so written the a wrong message:

Input:

<contract>
<contractID>123456</contractID>
<billingSummary>
<billingSummaryID>B123</billingSummaryID>
 </billingSummary>
</contract>

Now the problem is: When i drop above message in the input Queue of my flow. it is picked by the flow, but it is not showing where this message went.

in the even viewer below exception is: Message flow 'MyFlow_MF' could not be reconfigured because it remained busy for longer than the timeout period of '300000'

A request to reconfigure the message flow 'MyFlow_MF' was received but this could not be processed because it remained busy processing a message for longer than the timeout specified.

This can be caused by the timeout being too short considering the complexity of the flow and the size of the messages being processed. In such cases the timeout should be increased. It can also be caused by message flows containing infinite loops. In such cases the SQL should be corrected.

Even DB2 is throwing exception saying:

2009-07-17-11.14.58.859000 Instance:DB2 Node:000
PID:13132(db2fmp.exe) TID:13096 Appid:none
Health Monitor HealthIndicator::update Probe:500

ADM10500E Health indicator "Monitor Heap Utilization" ("db2.mon_heap_util")
breached the "upper" alarm threshold of "95 %" with value "124 %" on "instance"
"DB2". Calculation: "((db2.mon_heap_cur_size/db2.mon_heap_max_size)*100);" =
"((344064 / 278528) * 100)" = "124 %". History (Timestamp, Value, Formula): "
(07/17/2009 11:09:13.140000, 6, ((16384 / 278528) * 100)), (07/17/2009
11:04:13.359000, 6, ((16384 / 278528) * 100)), (07/17/2009 10:59:13.484000, 6,
((16384 / 278528) * 100)), (07/17/2009 10:55:47.156000, 6, ((16384 / 278528) *
100)), (07/17/2009 10:49:13.265000, 6, ((16384 / 278528) * 100)), (07/17/2009
10:44:13.187000, 6, ((16384 / 278528) * 100)), (07/17/2009 10:39:13.578000, 124,
((344064 / 278528) * 100)), (07/17/2009 10:35:30.109000, 6, ((16384 / 278528) *
100)), (07/17/2009 10:29:13.125000, 6, ((16384 / 278528) * 100))"

My understanding is if the incoming message fails, it should go to fail terminal of the input node. and in the variables column it will shown for element the validation is failing.

which is not happening in the above scenario.

Can any body please tell me why this is not shown in the debuger. where could be the problem.