PM36607: SPECIFYING '0' FOR SOAP REQUESTTIMEOUT PARAMETER CAUSES WCBD DEPLOY SCRIPT TO FAIL WITH SOAP TIMEOUT ISSUE

Fixes are available

APAR status

Closed as program error.

Error description

WCDB deploy script works on WC 7.0 and WebSphere Application
Server 7.0.0.9 on Sun Solaris 5.10, but fails with SOAP
TimeOut issue after upgrading to WC 7.0.0.2 and WebSphere
Application Server 7.0.0.15 on the same servers.

On WebSphere Application Server 7.0.0.15, the WCDB deploy
script is failing 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=0 is set to 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.

In the wcdb-deploy-server.log, we see 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

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:                                              *
****************************************************************
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
fixpacks 7.0.0.17 . Please refer to the recommended updates page
for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM36607
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-04-08
Closed date
2011-04-15
Last modified date
2011-04-15

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021

Tips

PM36607: SPECIFYING '0' FOR SOAP REQUESTTIMEOUT PARAMETER CAUSES WCBD DEPLOY SCRIPT TO FAIL WITH SOAP TIMEOUT ISSUE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?