Troubleshoot the run time for a Web services client

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

If you installed a Web service application that was developed for a WAS version prior to v6, you might get the following exception

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 V6.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 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.

To solve the problem, increase the ConnectionIOTimeOut parameter for the Web container HTTP transport. The default value is 5 seconds. Increase the value to 30 seconds or greater. Set the value using the administrative console. Click...

Servers | Application Servers | servername | Web Container | HTTP Transports | port_number | Custom Properties | New

Type the following property name and value:

Name: ConnectionIOTimeOut
Value: 30

If the Web service is hosted in a clustered environment, set the property on each application server in the cluster. If your application server is listening on more than one port number, set the property on all ports.

Related Tasks

Troubleshoot Web services