The first message above (SOAPException - Read timed out)
indicates the SOAP client on the addNode script side has timed out before
the operation was completed on the DMGR side. This can generally be
resolved by increasing the com.ibm.SOAP.requestTimeout setting in the
soap.client.props file (located in
/<configRoot>/AppServer/properties). Depending on how resource
constrained your system is, you may want to increase this value to 900 to
1200 seconds.
The RuntimeMBeanException above, followed by various other errors,
generally means a timeout occurred in the DMGR while the SOAP client was
awaiting a response on the script side. Check the controller and servant
region joblogs for an EC3 abend followed by a reason code. Using the
reason code found check this table to determine which timeout value should
be increased:
http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/abend02.htm
For example, if the reason code is 04130004, this indicates a WLM dispatch
timeout according to the table in the link above. The timeout variable to
increase in this case would be the
control_region_wlm_dispatch_timeout.
|