Forum Discussion
I'm not familiar with WS-Security or other features that may require access to the entire request. My understanding was that when MTOM was used, the file(s) included in the request were sent as MIME attachments outside of the soap envelope, I'm not sure if that helps in allowing the entire soap envelope to be accessed in memory while still streaming the attachment. If that is possible, then perhaps support for streaming could be available in combination with the use of MTOM.
I tried the June 6 soapUI 3.0 beta 1 build, with the chunking feature enabled. While soapUI did use chunking to send the request, it sent the entire request as one chunk (even with a document size of 10MB), and it appears to buffer the entire request in memory, which leads to java heap problems for the soapUI JVM (similar to what I have been seeing for download tests with large documents). I'm not sure if this is happening because the request is sent as one chunk and so is not broken up into smaller pieces to load into memory, or if it just a case where the entire request is always loaded into memory by soapUI.
In either case (chunking or not), a key requirement for me is to have soapUI not buffer the entire request in memory. I need to test uploading documents up to a size of 1GB, currently java heap usage is roughly 10x the document size so the largest document I can upload is about 100MB (with just one client thread).
Thanks,
Scott
I tried the June 6 soapUI 3.0 beta 1 build, with the chunking feature enabled. While soapUI did use chunking to send the request, it sent the entire request as one chunk (even with a document size of 10MB), and it appears to buffer the entire request in memory, which leads to java heap problems for the soapUI JVM (similar to what I have been seeing for download tests with large documents). I'm not sure if this is happening because the request is sent as one chunk and so is not broken up into smaller pieces to load into memory, or if it just a case where the entire request is always loaded into memory by soapUI.
In either case (chunking or not), a key requirement for me is to have soapUI not buffer the entire request in memory. I need to test uploading documents up to a size of 1GB, currently java heap usage is roughly 10x the document size so the largest document I can upload is about 100MB (with just one client thread).
Thanks,
Scott
Related Content
- 3 years ago
- 3 years ago
- 4 years ago
Recent Discussions
- 2 days ago
- 2 days ago