PH51280: JVM PROCESS WAS NOT STARTING, AFTER CUSTOMIZING / MODIFYING THE CIPHER LIST

APAR status

• Closed as program error.

Error description

• JVM was not starting after customizing the SSL configuration QoP
  setting with a custom cipher list, an issue with the parser with
  whitespace in the list.
  
  
  [12/1/22 12:59:49:007 EST] 00000001 FfdcProvider  W
  com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC
  Incident emitted on /apps/wasprofiles/dmgr-02/logs/ffdc/dmgr_1c
  d252d_22.12.01_12.59.48.9867825149507211130459.txtcom.ibm.ws.sec
  SLServerSocket459
  [12/1/22 12:59:49:076 EST] 00000001 FfdcProvider  W
  com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC
  Incident emitted on /apps/wasprofiles/dmgr-02/logs/ffdc/dmgr_1c
  d252d_22.12.01_12.59.49.0098074623747258667950.txtcom.ibm.ws.orb
  
  [12/1/22 12:59:49:079 EST] 00000001 ORBRas        E
  com.ibm.ws.orbimpl.transport.WSTransport createServerSocket
  P=586807:O=0:CT ORBX0390E: Cannot create listener thread.
  Exception=[ org.omg.CORBA.INTERNAL:
  CAUGHT_EXCEPTION_WHILE_CONFIGURING_SSL_SERVER_SOCKET,
  Exception=java.lang.IllegalArgumentException: The specified
  CipherSuites array contains invalid null or empty string
  elements  vmcid: 0x49421000  minor code: 77  completed: No -
  received while attempting to open server socket on port 9403 ].
  [12/1/22 12:59:49:107 EST] 00000001 FfdcProvider  W
  com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC
  Incident emitted on /apps/wasprofiles/dmgr-02/logs/ffdc/dmgr_1c
  d252d_22.12.01_12.59.49.0801527240966541278264.txtcom.ibm.ws.orb
  [12/1/22 12:59:49:127 EST] 00000001 FfdcProvider  W
  com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC
  Incident emitted on /apps/wasprofiles/dmgr-02/logs/ffdc/dmgr_1c
  d252d_22.12.01_12.59.49.1075399074290116962493.txtcom.ibm.ws.orb
  [12/1/22 12:59:49:127 EST] 00000001 WsServerImpl  E   WSVR0009E:
  Error occurred during startup
  com.ibm.ws.exception.RuntimeError: org.omg.CORBA.INTERNAL:
  CREATE_LISTENER_FAILED_4  vmcid: 0x49421000  minor code: 56
  completed: No
  at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:490)
  at com.ibm.ws.runtime.component.ContainerHelper.startComponents
  (ContainerHelper.java:540)
  at com.ibm.ws.runtime.component.ContainerImpl.startComponents(C
  ontainerImpl.java:627)
  at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerIm
  pl.java:618)
  at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.jav
  a:540)
  at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServer
  Impl.java:325)
  at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:238)
  at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:711)
  at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
  ssorImpl.java:90)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
  thodAccessorImpl.java:55)
  at java.lang.reflect.Method.invoke(Method.java:508)
  at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.jav
  a:234)
  at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:96)
  at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:77)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
  ssorImpl.java:90)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
  thodAccessorImpl.java:55)
  at java.lang.reflect.Method.invoke(Method.java:508)
  at org.eclipse.equinox.internal.app.EclipseAppContainer.callMet
  hodWithException(EclipseAppContainer.java:587)
  at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips
  eAppHandle.java:198)
  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher
  .runApplication(EclipseAppLauncher.java:110)
  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher
  .start(EclipseAppLauncher.java:79)
  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS
  tarter.java:369)
  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS
  tarter.java:179)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
  ssorImpl.java:90)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
  thodAccessorImpl.java:55)
  at java.lang.reflect.Method.invoke(Method.java:508)
  at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
  
  at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
  at org.eclipse.core.launcher.Main.run(Main.java:981)
  at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLau
  ncher.java:425)
  at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.jav
  a:178)
  Caused by: org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4
  vmcid: 0x49421000  minor code: 56  completed: No
  at com.ibm.ws.orbimpl.transport.WSTransport.createListener(WSTr
  ansport.java:867)
  at com.ibm.ws.orbimpl.transport.WSTransport.initTransports(WSTr
  ansport.java:605)
  at com.ibm.rmi.iiop.TransportManager.initTransports(TransportMa
  nager.java:157)
  at com.ibm.rmi.corba.ORB.set_parameters(ORB.java:1362)
  at com.ibm.CORBA.iiop.ORB.set_parameters(ORB.java:1697)
  at org.omg.CORBA.ORB.init(ORB.java:473)
  at
  com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
  at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
  at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java
  :102)
  at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:55)
  at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:482)
  ... 34 more
  

Local fix

•  Remove the TLSv1.3 cipher from list  --- if you are not using
  TLSv1.3 (sslProtocol="TLSv1.2")
   I removed the extra space character which is in between first
  and second cipher. then the dmgr is able to startup.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Server fails start if there are extra   *
  *                      spaces in a custom cipher list.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a customer creates a custom cipher list that has extra spaces
  between the ciphers then there will be error when the ciphers
  are
  set.  Depending on the SSLConfig in question the server may not
  start.
  

Problem conclusion

• Take into account extra white space when splitting the cipher li
  up.
  
  
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.23 and 9.0.5.15. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels