server启动故障：com.ibm.ws.exception.RuntimeError

问题描述：
在做了配置变更之后，server启动不起来。还原配置，依然存在这启动故障。

this is the log :

[8/23/15 12:09:20:276 CST] 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:489)
        at com.ibm.ws.runtime.component.ContainerHelper.startComponents(ContainerHelper.java:539)
        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:523)
        at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:310)
        at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:223)
        at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:686)
        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: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(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.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(EclipseStarter.java:369)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
        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:380)
        at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:151)
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:166)
        at com.ibm.rmi.corba.ORB.set_parameters(ORB.java:1277)
        at com.ibm.CORBA.iiop.ORB.set_parameters(ORB.java:1691)
        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:481)
        ... 34 more

百度搜索找到一篇有关的博文，推测可能是由于之前server启动导致进程挂起。查看进程状态，进程果然存在，杀掉对应的进程，重启server，启动正常