v4.0.1 - Read time outs snowball, lead to heap space error
I am using soap ui v4.0.1 to test a program I'm running on localhost.
If I don't restart soapui between tests, I begin to see response times increase predictably. I am looping one query 300 times, with a ten second delay between each query. Each response takes between 30-40 seconds if soapui has been freshly started.
If I keep soapui open for back to back 300 query tests, I start to see SocketTimeoutExceptions. Nearly all responses approach the 60 second mark, and after a while, I see nothing but read time outs. Eventually I receive an error, e.g., "Thu Dec 29 21:13:53 EST 2011:ERROR:java.lang.OutOfMemoryError: Java heap space." My local server is unaffected, and queries continue to respond in the 30 to 40 second range.
I learned from other posts that I can extend the timeout beyond 60 seconds using TestCase > TestCase options > Basic > SocketTimeout.
I want to know if extending the timeout will prolong the life of my test, i.e., Do read time outs have an especially adverse effect on the heap space soapui is using? Or is the heap space simply fillling up slowly, and an eventual crash inevitable?
Thank you for your response.
If I don't restart soapui between tests, I begin to see response times increase predictably. I am looping one query 300 times, with a ten second delay between each query. Each response takes between 30-40 seconds if soapui has been freshly started.
If I keep soapui open for back to back 300 query tests, I start to see SocketTimeoutExceptions. Nearly all responses approach the 60 second mark, and after a while, I see nothing but read time outs. Eventually I receive an error, e.g., "Thu Dec 29 21:13:53 EST 2011:ERROR:java.lang.OutOfMemoryError: Java heap space." My local server is unaffected, and queries continue to respond in the 30 to 40 second range.
I learned from other posts that I can extend the timeout beyond 60 seconds using TestCase > TestCase options > Basic > SocketTimeout.
I want to know if extending the timeout will prolong the life of my test, i.e., Do read time outs have an especially adverse effect on the heap space soapui is using? Or is the heap space simply fillling up slowly, and an eventual crash inevitable?
Thank you for your response.