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 Dain,
Sorry for the delay in responding, I've been sidetracked for a few weeks.
I think this would be a useful addition to soapUI, it would address my original requirement to execute the test with chunking enabled. Perhaps an incremental improvement would be to make this a property of the TestRequest, rather than a global preference, so that chunking could be enabled/disabled, and the size specified, on a per request basis.
I have an additional related question. As an alternative to enabling chunking, it should also be possible to avoid the memory issues I was experiencing by streaming the upload. I'm told that for a java client, that is sending requests directly using the HttpUrlConnection class, calling setFixedLengthStreamingMode (ContentLength) will enable streaming. For a java client using the jaxws library, it's not possible to call the above method directly on the underlying HttpUrlConnection, but a jaxws chunksize property can be set to cause it to call setChunkedStreamingMode(chunkLength) on the underlying HttpUrlConnection.
I was wondering if you could describe how soapUI is sending the WS requests internally, and whether it would be possible to also expose a configuration property that would enable streaming for the request?
Thanks,
Scott
Sorry for the delay in responding, I've been sidetracked for a few weeks.
I think this would be a useful addition to soapUI, it would address my original requirement to execute the test with chunking enabled. Perhaps an incremental improvement would be to make this a property of the TestRequest, rather than a global preference, so that chunking could be enabled/disabled, and the size specified, on a per request basis.
I have an additional related question. As an alternative to enabling chunking, it should also be possible to avoid the memory issues I was experiencing by streaming the upload. I'm told that for a java client, that is sending requests directly using the HttpUrlConnection class, calling setFixedLengthStreamingMode (ContentLength) will enable streaming. For a java client using the jaxws library, it's not possible to call the above method directly on the underlying HttpUrlConnection, but a jaxws chunksize property can be set to cause it to call setChunkedStreamingMode(chunkLength) on the underlying HttpUrlConnection.
I was wondering if you could describe how soapUI is sending the WS requests internally, and whether it would be possible to also expose a configuration property that would enable streaming for the request?
Thanks,
Scott
