How to handle large reponses with SOAP.OutboundAdapter

Question

Question

Michael Lundberg · Feb 12, 2016

Hi,

We do have a production including a SOAP.OutboundAdapter that make a request to a .NET WCF Service. The response from that service vary in size. When it come to large one, we talk about maybe 8000 records (with 6-8 attributes per record) in xml, the adapter always give a timout. Even if we put a high number of seconds or set -1. After 1 1/2h still nothing get back. It's just standing there and waiting for ever.

Our .NET developer have look at it (on the WCF-service) and from ther point of view they say that it seems like Ensemle can't handle such big responses.

In .Net it.s possible to put the property "maxReceivedMessageSize" when they expecting large size responses.

Is it possible to do the same in ensemble or is it another best practise to solve this problem?

Sincerely, Michael Lundberg

Discussion (2)1

Log in or sign up to continue

Stefan Wittmann · Feb 12, 2016

Hi Michael,

did you check the trace for errors? A first guess is that the process throws a <STORE> error when it tries to validate the response. Increasing the maximum per process memory might help. Here is the related documentation:

http://docs.intersystems.com/enscomm20152/csp/docbook/DocBook.UI.Page.cls?KEY=GSA_config#GSA_config_system_startup

Stefan

0 0

score 0 · Answer 1 · 2016-02-12T10:09:23-05:00

Hi and thanks for answer.

No i can't find any <STORE> exceptions in the trace. Actually everythings goes fine from service->process->operation. It just stuck there after the request. Messagestate for process is "Delivered"

I have also checked the processes in system operation/processes and all processes for current namespace are in state of EVTW.

The Net.HttpRequest process in state of READ

However it might be a memory problem as you think and we have to check it out

Michael