transfer-encoding:chunked for WS request
I am using soapUI 2.5.1 to test uploading documents to a WS using MTOM. By default I am seeing very high memory usage (10 X doc size) in the java heap both in soapUI client, and in the java server. ...
Forum Discussion
Hi Scott,
thanks for all your thoughts and insights!
soapUI 3.0 improved on the global chunking setting; it allows you to set a chunking limit; if the size of the request is larger, it will be chunked. Moving this to the request level as well would be relatively easy if you find it motivated.
soapUI uses the HttpClient library internally for sending requests, which supports streaming (via the requestentity related classes I think), but this would require some work since we still need to support property-expansions, ws-security, etc.. which require access to parts or the entire request (for example for signing..)
looking forward to your ideas!
/Ole
eviware.com
thanks for all your thoughts and insights!
soapUI 3.0 improved on the global chunking setting; it allows you to set a chunking limit; if the size of the request is larger, it will be chunked. Moving this to the request level as well would be relatively easy if you find it motivated.
soapUI uses the HttpClient library internally for sending requests, which supports streaming (via the requestentity related classes I think), but this would require some work since we still need to support property-expansions, ws-security, etc.. which require access to parts or the entire request (for example for signing..)
looking forward to your ideas!
/Ole
eviware.com
