|
Home > Archive > WebSphere Portal Server > March 2007 > Portal 6 server can't be started
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Portal 6 server can't be started
|
|
|
| hi,
I have just finished installing portal 6 on my machine (win xp sp2)
and I tried starting portal 6 server, and it works, then I tried to open the portal6 starting page with my browser, and it works just fine too.
The problem happened after I restart my machine, and I try to start the portal 6 server again, but It can't. I didn't change any configuration for the server. I ONLY restart my machine. I tried to look at the systemout.log and I found this message
[3/25/07 14:31:20:562 ICT] 0000000a WsServerImpl E WSVR0009E: Error occurred during startup
com.ibm.ws.exception.RuntimeError: 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.WsServerImpl.bootServerContainer(WsServerImpl.java:194)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:570)
Caused by: 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:366)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187)
... 10 more
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:733)
at com.ibm.ws.orbimpl.transport.WSTransport.initTransports(WSTransport.java:605)
at com.ibm.rmi.iiop.TransportManager.initTransports(TransportManager.java:143)
at com.ibm.rmi.corba.ORB.set_parameters(ORB.java:1298)
at com.ibm.CORBA.iiop.ORB.set_parameters(ORB.java:1848)
at org.omg.CORBA.ORB.init(ORB.java:368)
at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:85)
at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:174)
at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:124)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:339)
at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:359)
... 14 more
Can you guys help me with my problem please
thank you
| |
|
| Did you configure portal to start as a service under XP or to start manually ?
if you configured it to start as a service, check if it starts successfully via the Services window.
Generally its not a good idea to configure it to run as a service under XP - its easier to do the start/stop manually.
| |
|
| I didn't configure it as window service, so I start and stop it manual.
I find the real problem now, it says
com.ibm.ws.orbimpl.transport.WSTransport createServerSocket Thread-1 ORBX0390E: Cannot create listener thread. Exception=[ org.omg.CORBA.INTERNAL: CAUGHT_EXCEPTION_WHILE_CONFIGURING_SSL_S
ERVER_SOCKET, Exception=org.omg.CORBA.INTERNAL: UNABLE_TO_CREATE_SSL
_SERVER_SOCKET Exception=java.net.BindException: Address already in use: NET_Bind vmcid: 0x49421000 minor code: 76 completed: No vmcid: 0x49421000 minor code: 77 completed: No ].
do you have idea what the address is ?
I have DB2 enterprise edition 8.2 in my machine, is it the problem ?
thanks for the advice
| |
|
| I you haven't externalised to DB2 as yet then I'd struggle to understand how DB2 would be causing a problem with Portal.
Try stopping DB2 and then starting Portal.
The error seems to suggest it cannot create a listener service on the Portal SSL port, which should be 10039 (or 10003 for WAS6). Shutdown Portal and DB2 and then check if you have other services listening on that port (use netstat to do this).
|
|
|
|
|