Hello Everyone,
Hope you all are
enjoying working with the Middleware .Today I am getting error while starting
the JVM in WebSphere Application Server environment v8.5.0.2. and it's not
getting started. When I checked the SystemOut.log found the below error
description.
Error:
[11/8/16 0:11:44:222
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(ContainerImpl.java:627)
at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:618)
at
com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:540)
at
com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:311)
at
com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:224)
at
com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:697)
at
com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at
java.lang.reflect.Method.invoke(Method.java:613)
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:88)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at
java.lang.reflect.Method.invoke(Method.java:613)
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:88)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at
java.lang.reflect.Method.invoke(Method.java:613)
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:401)
at
com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:164)
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:155)
at
com.ibm.rmi.corba.ORB.set_parameters(ORB.java:1274)
at
com.ibm.CORBA.iiop.ORB.set_parameters(ORB.java:1688)
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:482)
... 34 more
Couse :
The main reason of
this error is port conflict. It means the ports of JVM which you are trying to
start are already being used by some other process on servers.
Solution:
First login to the console or from backend list down all the ports which your JVM is listening.
Console: login > Server > ServerName >Ports
Backend: /IBM/WebSphere85/profiles/AppSrv01/config/cells/CellName/nodes/NodeName/serverindex.xml
Check if the ports are already listening.
netstat -an | grep PortNo.
If any port is already listening find out the process running on it.
netstat -tcpl | grep PortNo.
Kill the Process running on the port.
Kill -9 Process Id
Try to start the JVM again and this time it will start the JVM.
Hope this will help
you. Kindly comment for your suggestion and quires.
"Effort only fully releases its reward after a
person refuses to quit.”
Regards,
Akhilesh B.
Humbe
