WebSphere Commerce Version 8.0.4.0

Troubleshooting: Installation of WebSphere Commerce Developer 8.0.4 hangs

If you think the installation of WebSphere Commerce Developer Version 8 Mod Pack 4 (8.0.4) is taking a long time to complete, then verify whether the installation process is hung or still executing.

If you are using the Installation Manager, you might notice that the Updating: Applying fix pack progress bar on the Update packages panel stays at the same position for a long time. Use the following methods to verify that your installation stalled.
  • Open Task Manager. You might notice that there are Java processes running with 0% CPU usage.
  • Check the following log file WCDE_installdir\logs\updateModules.log. You might find the following error:
    BUILD FAILED
    C:\IBM\WCDE80\components\common\xml\updateModules.xml:51: The following error occurred while executing this line:
    C:\IBM\WCDE80\components\common\xml\updateModules.xml:88: 
    Server WebSphere Commerce Test Server was unable to start within 600 seconds. 
    If the server requires more time, try increasing the timeout in the server editor.
  • Check the System.out log file. You might find that the following error is repeated multiple times:
    [1/23/17 9:26:34:953 CST] 00000091 SSLHandshakeE E   SSLC0008E: Unable to initialize SSL connection.  
    Unauthorized access was denied or security settings have expired.  Exception is javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
    	at com.ibm.jsse2.b.a(b.java:80)
    	at com.ibm.jsse2.nc.a(nc.java:223)
    	at com.ibm.jsse2.nc.unwrap(nc.java:293)
    	at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:3)
    	at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.readyInbound(SSLConnectionLink.java:536)
    	at com.ibm.ws.ssl.channel.impl.SSLConnectionLink.ready(SSLConnectionLink.java:296)
    	at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214)
    	at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113)
    	at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
    	at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
    	at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
    	at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
    	at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
    	at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
    	at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
    	at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1881)

Problem

WebSphere Application Server administrative security is stopping the WebSphere Commerce Test server from starting due to an expired certificate, which halts the installation.

Solution

  1. End the current installation process through the Task Manager.
    • End the Java processes that are running with 0% CPU usage.
    • End the IBM Installation Manager process (IBMIM.exe).
  2. Disable WebSphere Application Server administrative security.
  3. Restart the installation.
  4. Renew the certificate. For more information about how to renew, see the following WebSphere Application Server documentation Renewing a certificate in SSL.
  5. Re-enable WebSphere Application Server administrative security.