Hi,

I tried to isolate this issue on the simplest orchestration, which only includes an interaction with an outside webservice published through the internet. Initially, we used the SOAP adapter but gradually changed to WCF-Custom adapter; now all ports are set to use this adaoter. Well, we changed some maps to perform using xslt only, no direct binding in the mapper by itself, to discard possible negative effects inducted by the mapper. The schema is part of a multipart message that was created through the web service discovery so a proxy was created to download all these schemas. It is a kind-of complex schema, it is long, BUT we use only like 15% of the whole schema.

So, here is my next question, memory-wise, what happens when we map complex schemas but you're not using the whole thing ? I've read about some properties, used commonly in the HL7, that is "GenerateDefaultFixedNodes", I tried by setting to "NO" in my original map, however was no use at all (same thing happened). By changing to xslt maps, the issue may disappear but there is still where you receive the response message (which is a message part of the complex schema).