WebSphere Commerce instance creation fails with ConfigServiceException Technote
(troubleshooting)Problem(Abstract) The following exception appears in the createInstanceAnt.log after a failed instance creation:
WASX7017E: Exception received while running file "/opt/IBM/WebSphere/CommerceServer60/config/deployment/scripts/createVirtualHosts.jacl"; exception information: com.ibm.websphere.management.exception.ConfigServiceException
The createInstanceAnt.log and createInstanceAnt.err.log are located under WC_installDir/instances/<instance>/logs.
The createInstanceAnt.err.log shows a stack similar to this:
file:/opt/IBM/WebSphere/CommerceServer60/config/deployment/xml/configureAppServer.xml:193: Java returned: 105
at org.apache.tools.ant.taskdefs.Java.execute(Java.java:110)
at com.ibm.websphere.ant.tasks.WsAdmin.execute(WsAdmin.java:386)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
at org.apache.tools.ant.Task.perform(Task.java(Compiled Code))
at org.apache.tools.ant.Target.execute(Target.java(Compiled Code))
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:143)
at org.apache.tools.ant.Task.perform(Task.java(Compiled Code))
at org.apache.tools.ant.Target.execute(Target.java(Compiled Code))
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
at org.apache.tools.ant.Task.perform(Task.java(Compiled Code))
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
at com.ibm.commerce.config.ant.server.QuickDeployment.startDeployment(QuickDeployment.java:481)
at com.ibm.commerce.config.server.CMServerImpl.startDeployment(CMServerImpl.java:2017)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java(Compiled Code))
at sun.rmi.transport.Transport$1.run(Transport.java(Compiled Code))
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at sun.rmi.transport.Transport.serviceCall(Transport.java(Compiled Code))
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java(Compiled Code))
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.handleRequest(TCPTransport.java:837)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:911)
at java.lang.Thread.run(Thread.java:570)
[2007.03.26 11:24:54] BUILD FAILED
file:/opt/IBM/WebSphere/CommerceServer60/config/deployment/xml/configureAppServer.xml:193: Java returned: 105
Total time: 25 minutes 17 seconds
Cause The default timeout value for SOAP is 180 seconds which may be too low in some cases. Resolving the problem Back up and edit the file called soap.client.props, located under /WAS_profileDir/demo/properties
Locate the following section:
------------------------------------------------
#------------------------------------------------------------------------------
# SOAP Request Timeout
#
# - timeout (specified in seconds [default 180], 0 implies no timeout)
#
#------------------------------------------------------------------------------
com.ibm.SOAP.requestTimeout=180------------------------------------------------
Update the timeout value to either 0 (for no timeout) or a higher number, for instance 3600 (1 hour).
After updating the timeout value, you can resume your instance creation by using either the config_ant script or the Configuration Manager.
You can run the config_ant script as follows:
From your WC_install/bin directory, run the following command:
config_ant.sh -DinstnaceName=<your instance> CreateVirtualHosts
Document Information Current web document: http://www.ibm.com/support/docview.wss?uid=swg21260856