It is still usefull after 9 years , the navigation path has changed a bit on the console that's it. Thank you John!
john randolf wrote:i had the exact same problem...It was KILLING our production system. it was happening to anyone with a modem....heres the fix :
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, 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. Set the value using the administrative console. Click Servers > Application Servers > server_name > 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.