|
Problem(Abstract) |
On one node you are running IBM WebSphere Application
Server V5.0 Network Deployment with deployment manager. On another node
you are running Application Server V5.0 Base. When running the startServer
command from your Base node, you receive a WASX7120E error, followed by a
SOAPException exception. |
|
|
|
Cause |
Invoking a scripting process from your Base node,
$Base_Root/bin> wsadmin.bat/sh
then running the startServer command,
wsadmin>$AdminControl startServer <server> <base-node>
generates the following errors:
WASX7120E: Diagnostic information from exception with text
"com.ibm.websphere.management.exception.ConnectorException
org.apache.soap.SOAPException:[SOAPException:faultCode=SOAP-ENV:Clie
nt;msg=Read timed out;
targetException=java.io.InterruptedIOException: Read timed out]"
follows: com.ibm.websphere.management.exception.ConnectorException:
ADMC0009E: Failed to make the SOAP RPC call: invoke
The errors indicate that the request is timing out before it
completes.
|
|
|
Resolving the
problem |
Resolve this problem by increasing the time that your
Application Server has to complete the operation. Change the
RequestTimeout value in your SOAP properties file on the
Application Server V5.0 Base node to a larger value. The default value is
180 seconds. Try setting the value to 600 seconds to see if
this adjustment helps.
To change the default value, edit the following line within your
$WAS_HOME\properties\soap.client.props file:
com.ibm.SOAP.requestTimeout=600 |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|