This topic discusses troubleshooting Web services clients.
Each section in this topic is a problem that you might experience during the run-time of a Web services client. A solution is provided to help you troubleshoot the problem.
Runtime migration error
WSWS3701E: Error: An exception was encountered. Use wsdeploy to deploy your application. This may correct the problem. The exception is <exception data>.
This exception indicates that a problem occurred while running the application that was developed with tools supported by versions prior to Version 6.0. A solution to the problem is to uninstall the application, run the wsdeploy command and redeploy the application.
WebServicesFault exception displays during the application server run time for certain Web Services Description Language (WSDL) files
A WebServicesFault exception displays during the application server run time for WSDL files that define operations with document style and literal use, and use the SOAP header to transmit the input data.
If the WSDL files define the operation with document style and literal use, and this operation maps the input to the SOAP header, the Web services run time fails to find the correct operation for the target service and the WebServicesFault exception displays.
To solve the problem, change the WSDL files so that the operation does not have input that uses the SOAP header to transmit the data.
Increase the value of the ConnectionIOTimeOut parameter to avoid receiving an exception when hosting Web services on WebSphere Application Server
When hosting Web services on WebSphere Application Server, the following exception displays: java.net.SocketTimeOutException: Read Timed Out.
A slow network connection between the client and the Web service causes this problem. In such cases, the HTTP socket might time out before the Web service engine completely reads the SOAP request. In the majority of cases, a sudden increase in overall network activity causes this problem. The problem can also occur when the client is accessing the Web service from a slow network connection and when the SOAP request has a lot of data.
Running a Web services client application with session persistence turned on might cause a WebServicesFalut error
[mm/dd/yy hh:mm:ss:ttt EST] 0000006e SystemErr R WebServicesFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException faultString: java.io.IOException: Connection close: Read failed.Possible end of stream encountered. faultActor: null faultDetail:You can avoid this error by following one of two ways:
The advantage to choosing this way to avoid the error, is that the IBM HTTP Server does not shut down idle or near-idle connections. The disadvantage to this choice is that the IBM HTTP Server uses excess resources to keep extra threads available, even during periods of light activity. This choice can only be done on a Unix platform.
Related tasks
Troubleshooting Web services