Socket read errors on LAN when reading WSDL or SOAP messages
We're running into socket read errors when using SOAPUI to fetch WSDL or SOAP responses on a LAN. It happens somewhat intermittently, and only with servers that have very low latency. For example, it happens with servers on the same host that SOAPUI is running on (localhost) or on the same LAN segment as the SOAPUI client machine.
No other SOAP clients or tools exhibit this problem, only SOAPUI. We have tried it with SOAPUI 4.5.0 and 4.5.1, and this is preventing us from using the software at all.
In these cases, SOAPUI will either fail to fetch the WSDL, or will read only a partial SOAP response message and then quit. If we look in the XML view of the response, it is either empty or incomplete. It sounds like it might be related to this user's post: http://www.soapui.org/forum/viewtopic.php?f=4&t=16178
SOAPUI logs this error:
The servers we're using are written in Java, and doing very simple servlet stream writes to send the WSDL and SOAP responses. We have debugged and instrumented the server-side code, and found that in each case the server completes the response in < 1 second and successfully writes and flushes the outbound stream socket. It works fine with many other client tools, including XMLSpy, Eclipse, and Firefox -- never any issue except with SOAPUI.
One interesting thing here is that when we step through the server code very slowly, SOAPUI successfully reads the response -- but only if the server takes 5-10 seconds to produce the response. If it is fast (sub second), then SOAPUI fails on the read or reads an incomplete message.
We really need a resolution on this. We opened a ticket with the support team, but they have gone silent for the last 5 days. We are a software vendor, and we have been recommending SOAPUI to all our customers as a testing platform. However, if this issue cannot be resolved, we will have to retract that recommendation and find another tool. Today another of our customers ran into this issue using SOAPUI, as well, and it was an embarrassing situation for all since SOAPUI did not perform as advertised.
If there is anything more I can include to help resolve this, please let me know. Thank you.
No other SOAP clients or tools exhibit this problem, only SOAPUI. We have tried it with SOAPUI 4.5.0 and 4.5.1, and this is preventing us from using the software at all.
In these cases, SOAPUI will either fail to fetch the WSDL, or will read only a partial SOAP response message and then quit. If we look in the XML view of the response, it is either empty or incomplete. It sounds like it might be related to this user's post: http://www.soapui.org/forum/viewtopic.php?f=4&t=16178
SOAPUI logs this error:
Error loading [http://localhost:9090/sampleapp/Simple/Simple.wsdl]: java.net.SocketTimeoutException: Read timed out
The servers we're using are written in Java, and doing very simple servlet stream writes to send the WSDL and SOAP responses. We have debugged and instrumented the server-side code, and found that in each case the server completes the response in < 1 second and successfully writes and flushes the outbound stream socket. It works fine with many other client tools, including XMLSpy, Eclipse, and Firefox -- never any issue except with SOAPUI.
One interesting thing here is that when we step through the server code very slowly, SOAPUI successfully reads the response -- but only if the server takes 5-10 seconds to produce the response. If it is fast (sub second), then SOAPUI fails on the read or reads an incomplete message.
We really need a resolution on this. We opened a ticket with the support team, but they have gone silent for the last 5 days. We are a software vendor, and we have been recommending SOAPUI to all our customers as a testing platform. However, if this issue cannot be resolved, we will have to retract that recommendation and find another tool. Today another of our customers ran into this issue using SOAPUI, as well, and it was an embarrassing situation for all since SOAPUI did not perform as advertised.
If there is anything more I can include to help resolve this, please let me know. Thank you.