Socket Timeout when testing Mock Server
Hey guys, I've written a mock for a web service and tried to test it by sending a request via soapUI. The mock consists of a bunch of java classes. It's only task is to receive an incoming reque...
Forum Discussion
I developed a little test client which sends a request.xml and waits for the response.xml, just as I expect soapUI to do.
There is no problem at all. The communication runs fast and smooth. I (speaking as the client) get my response.xml
immediately after sending the response. After that the socket is closed and I'm able to send the next request.
So, there must be some error in my soapUI configuration.
What I observed as well:
If I configure the timeout in the GUI of soapUI to be 5000 (ms), instead of 50, I expected soapUI to wait 5 seconds
AFTER sending the request, before shutting down the socket. However, it seems that it waits 5 seconds BEFORE
sending the request to the server. I noticed that because my server got the request messages 5 seconds later.
This is utterly strange behavior, isn't it?
There is no problem at all. The communication runs fast and smooth. I (speaking as the client) get my response.xml
immediately after sending the response. After that the socket is closed and I'm able to send the next request.
So, there must be some error in my soapUI configuration.
What I observed as well:
If I configure the timeout in the GUI of soapUI to be 5000 (ms), instead of 50, I expected soapUI to wait 5 seconds
AFTER sending the request, before shutting down the socket. However, it seems that it waits 5 seconds BEFORE
sending the request to the server. I noticed that because my server got the request messages 5 seconds later.
This is utterly strange behavior, isn't it?