Contributions
Re: Error getting Response; null
Great! Thanks alot. This is exactly what I needed. Interestingly, you don't need to set a response size limit for this to work. Leaving 0 in the field you will still get the full response in the response pane. Still works great and I get the file to use/parse/test/save/compare/etc. Also, the file location must be a known subdirectory. Missing subdirectories will not get created.12 years agoPlace ReadyAPI QuestionsReadyAPI Questions11KViews0likes0CommentsError getting Response; null
I have a SOAP call that returns a large amount of data - approximately 73 MB. When I first open SoapUI this call will load correctly. SoapUI memory log indicates 831MB used. If I rerun the call (green arrow) I get the error in the subject line of this post. The HTTP Log shows that the response is fully recieved. It appears that if the action of running a call would clear out the response and release the used memory that SoapUI might function as excepted. I can close the app and reopen it to get the call to work again so this seems reasonable. Another option could be to allow the response to be removed by the user.Solved12 years agoPlace ReadyAPI QuestionsReadyAPI Questions13KViews0likes3Comments