Troubleshoot: Web services client run-time environment

This topic discusses troubleshooting Web services clients that are developed and implemented based on the Web services for Java 2 platform, Enterprise Edition (J2EE) specification.

Increase the value of the ConnectionIOTimeOut parameter to avoid receiving an exception when hosting Web services on WebSphere Application Server - Epxress

When hosting Web services on WebSphere Application Server - Express, you can receive the following exception:

java.long.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. Sudden increases in overall network activity cause this problem inmost cases. The problem can also occur when the client is accessing the Web service from a slow network connection and in situations where the amount of data in the SOAP request is large.

To solve the problem, increase the ConnectionIOTimeOut parameter for your Web container HTTP transport. The default value is 5 seconds. You can increase the value 30 seconds or greater.

Perform the following steps to set the ConnectionIOTimeOut value:

  1. Start the administrative console.
  2. Expand Servers, and click Application Servers.
  3. Click your server name.
  4. Under the Additional properties heading, click Web Container.
  5. Under the Additional properties heading, click HTTP Transports.
  6. Click your port number.
  7. Under the Additional properties heading, click Custom Properties.
  8. Click New.
  9. Specify the following property name and value:
  10. Click OK.

If your application server is listening on more than one port number, set the property on all ports.