WebSphere v7.0无法启动CREATE_LISTENER_FAILED_4

时间:2019-08-26 08:11:22

标签: websphere-7

我使用WebSphere v7.0。当我尝试启动服务器时,在控制台上出现以下错误。

[26/08/19 10:02:35:224 CEST] 00000000 WsServerImpl  E   WSVR0009E: Se ha producido un error durante el inicio
 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:439)
    at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:538)
    at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:627)
    at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)
    at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:502)
    at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:298)
    at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:214)
    at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:666)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)
    at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
    at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    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(WSPreLauncher.java:341)
    at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:111)
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(WSTransport.java:867)
    at com.ibm.ws.orbimpl.transport.WSTransport.initTransports(WSTransport.java:605)
    at com.ibm.rmi.iiop.TransportManager.initTransports(TransportManager.java:157)
    at com.ibm.rmi.corba.ORB.set_parameters(ORB.java:1303)
    at com.ibm.CORBA.iiop.ORB.set_parameters(ORB.java:1690)
    at org.omg.CORBA.ORB.init(ORB.java:364)
    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:432)
    ... 29 more

[26/08/19 10:02:35:135 CEST] 00000000 FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvid

我检查了serverindex.xml文件中的端口BOOTSTRAP_ADDRESS

 <specialEndpoints xmi:id="NamedEndPoint_1183122129640" endPointName="BOOTSTRAP_ADDRESS">
      <endPoint xmi:id="EndPoint_1183122129640" host="F120000.cargas02.sir" port="2809"/>
    </specialEndpoints>

输出命令netstat -ano是

TCP    0.0.0.0:2809           0.0.0.0:0              LISTENING       4072

如何解决此错误?

1 个答案:

答案 0 :(得分:0)

通常发生ORB Listener Thread创建失败的原因是:

  1. 另一个进程已经在侦听该端口(在本例中为2809)。
  2. ephemeral port range已在OS上进行了扩展,以使WebSphere服务器端口范围(2800-〜10000)现在包含在该范围内,从而增加了WAS服务器端口号被分配给另一个进程的可能性,例如临时端口。

对于场景#1 :使用netstat -anolsof -i :<port#>命令并搜索端口以使用该端口查找进程。如果发现有冲突的进程,请更改该进程的配置/端口用法。或在 dmgr-profile-root / config / cells / cellName / nodes / nodename 中编辑WebSphere serverindex.xml文件(确保事先进行备份)。将2809端口更改为另一个未使用的端口。保存并同步更改。

对于场景2 :选中服务器框上的ephemeral port range(基于OS的互联网搜索将对此提供具体说明)。确保端口范围的低端足够大于serverindex.xml文件中找到的最高WebSphere服务器端口。

最后,也有可能WebSphere服务器没有正确关闭并关闭其先前运行的所有端口。可能需要重新启动操作系统才能释放端口。