Significance of ConnectionlOTimeOut parameter in WebSphere Application Server

When hosting the Enterprise Application on WebSphere Application Server, sometimes its possible to receive the following exception:

java.net.SocketTimeOutException: Read Timed Out. (in SystemOut.log or activity.log).

Possible Root Cause:

A slow network connection between the client and the server causes this problem. In such cases, the HTTP socket might time out before the server completely reads the SOAP request. Sudden increase in overall network activity can also cause this problem The problem can also occur when the client is accessing the service from the server in a slow network connection and in situations where the amount of data in the SOAP request is large.

Possible solution:

Setting an appropriate value in the ConnectionlOTimeOut parameter might help to resolve the above issue. This parameter is configured under Web Container HTTP Transport (e.g 9080).
The default value is 5 seconds for the ConnectionlOTimeOut parameter for your Web container HTTP transport .

Thanks
A.T.J