Is there any way you can give us a reproducible test case for this one?
I asked David Ward about this one and he suggested that possibly the error SOAPUI is getting is causing it not to cache (and then refetching it over and over again while still getting the error).
Do you see the same sort of behavior with other webservices (maybe it has something to do with the one you are using)?
we have tested the same webservices using other frameworks like Sonic WSI framework which uses axis framework built in, in it.
frequently facing the out of memory errors because of this.
will be attaching the log for your understanding.
I could share the wsdl, could you able to expose the wsdl using Soap UI for testing?
Would appreciate if you can share some fine tuning details wrt SOAPclient usage. I'm concerned about the behavior and stability of the SOAPClient.