Troubleshooting: error logged

A is met while performing a WebSphere Application Server operation over SOAP.


WebSphere Commerce provides scripts and tools that update and deploy changes to your WebSphere Commerce instance (EAR file). The scenarios affected include, but are not limited to, the following:
  • WebSphere Commerce fix pack install or uninstall
  • interim fix install or uninstall
  • WebSphere Commerce Build and Deploy (WCBD) deployment,
  • feature enablement or disablement
  • migration

These WebSphere Commerce scripts and tools set the value in soap.client.props value to 0 to ensure that the deployment and update processes are given sufficient time to complete. However, there is an issue in WebSphere Application Server Version 7 fix pack 15 (v7.0.0.15) that causes the SOAP timeout to be ignored. When the value in soap.client.props is set to 0, a SOAP request time out still occurs with operations that take over 10 minutes.

The problem described here is limited to WebSphere Application Server v7 fix pack 15 (

Depending on the scenario where the error is encountered, the message in the logs might be similar to the following:

WASX7017E: Exception received while running file "/opt/IBM/WebSphere/CommerceServer70/components/store-enhancements/scripts/disableFeature.jacl"; 
   exception information:
org.apache.soap.SOAPException: [SOAPException: faultCode=SOAP-ENV:Client; msg=Read timed out; Read timed out]

WASX7341W: No "save" was performed before the interactive scripting session exited; configuration changes will not be saved.



Use one of these solutions: