MQSeries.net :: View topic

nxg912 · Posted: Fri Jan 08, 2010 10:21 am Post subject:

We have couple of message flows deployed on a EG but the incoming message XML is large (around 10Mb) and the flows involve a bunch of internal processing as well. We are noticing that as the flow processes the data, the EG's memory footprint keep rising and eventually the EG crashes. We have tried increasing the stack size and the JVM heap size as well. Another interesting thing is that even when the flow finishes (with smaller input message like 5Mb), the memory footprint never comes down after the completion of flow and the next flow execution fails very quickly because of memory. Do we need to do some explicit memory releases for our flow once it finishes or the EG should release this memory once the flow finishes? This way it seems that EG will alays fail even if we run smaller input message but run them large number of times. Is there a way to check and print programatically (ESQL or Java etc) the EG memory consumption in order to pin point where the memory consumption is rising? This flow does involve a bunch of SOAP requests to third party (and we notice no issue there as response comes back with in 30 seconds) and the number of SOAP requests never exceed 20 although they all involve response extraction and flow's internal processing.