PM36607; 7.0.0.15: The socket timeout is not set to 0

Download Description

Description/symptom of problem:
PM36607 resolves the following problem:

ERROR DESCRIPTION:
On WebSphere Application Server 7.0.0.15, deploy scripts fail with SOAP TimeOut issue, but in the Dmgr and individual profiles under PROFILE_HOME/properties/soap.client.props, the value of com.ibm.SOAP.requestTimeOut is set to zero which is no timeout.

Also, in the deploy-dev-prev.properties file, the timeout value is set to 9000, but still the client is getting timeout exception and the script is failing.

The wcdb-deploy-server.log, there are the following entries:
...

[wsadmin] Update of WC_preview has ended.
[wsadmin] Ended: 2011/04/06 16:57:36
[wsadmin] Saving configuration.
[wsadmin] Started: 2011/04/06 16:57:36
[wsadmin] WASX7017E: Exception received while running file
"/data/ecom/applications/wcbd-deploy-server-1.0/scripts/wcbd-wsa
dmin.py"
; exception information:
com.ibm.websphere.management.exception.ConnectorException
[wsadmin] org.apache.soap.SOAPException: [SOAPException:
faultCode=SOAP-ENV:Client; msg=Read timed out;
targetException=java.net.SocketTimeoutException: Read timed out]
[wsadmin]
/data/ecom/applications/wcbd-deploy-server-1.0/gehc-deploy.xml:8
6: The
following error occurred while executing this line:
/data/ecom/applications/wcbd-deploy-server-1.0/gehc-deploy.xml:1
46: The
following error occurred while executing this line:
/data/ecom/applications/wcbd-deploy-server-1.0/wcbd-deploy-commo
n.xml:16
23: The following error occurred while executing this line:
/data/ecom/applications/wcbd-deploy-server-1.0/wcbd-deploy-commo
n.xml:18
22: Java returned: 105
at
org.apache.tools.ant.ProjectHelper.addLocationToBuildException(P
rojectHe
lper.java:551)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:444)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:
291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
Accessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtil
s.java:1
06)
at org.apache.tools.ant.Task.perform(Task.java:348)
at
org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java
:68)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
Impl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
Accessor
Impl.java:25)
...

LOCAL FIX:
NONE

PROBLEM SUMMARY

USERS AFFECTED:
All users of IBM WebSphere Application Server version 7.0

PROBLEM DESCRIPTION:
The socket timeout is not set to 0 when SOAP requestTimeout is set to 0.

RECOMMENDATION:
None

When SOAP requestTimeout is 0, the socket timeout is not correctly set to 0, instead it times out after 10 minutes, and a ConnectorException is thrown:
com.ibm.websphere.management.exception.
ConnectorException
org.apache.soap.SOAPException:
[SOAPException:
faultCode=SOAP-ENV:Client; msg=Read timed out;
targetException=java.net.SocketTimeoutException:
Read timed out]

PROBLEM CONCLUSION:
Code was updated to set the socket timeout correctly. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.17 . Please refer to the recommended updates page for delivery information:
http://www.ibm.com/support/docview.wss?uid=swg27004980