Unable to initialize the server: Server failed to bind to the requested por

Question

I am facing the error while starting the server. I see the following error.
<Sep 26, 2007 11:49:54 PM EDT> <Emergency> <WebLogicServer> <BEA-000350> <Unable to create a server socket on Channel Default for: 162.86.20.87, port: 8101. java.net.BindException: Address already in use Perhaps the address 162.86.20.87 is incorrect or another process is using port 8101.>
<Sep 26, 2007 11:49:54 PM EDT> <Emergency> <Security> <BEA-090085> <Server failed to bind to the configured port. The port may already be used by another process.>
<Sep 26, 2007 11:49:54 PM EDT> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: Server failed to bind to the requested port. See preceeding log message for details.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.server.ServerLifecycleException: Server failed to bind to the requested port. See preceeding log message for details.'
Reason: Server failed to bind to the requested port. See preceeding log message for details.
If the port is already in use how to find which server is running on that port, how to find the process and kill it. I am using weblogic 8.1 sp4 in Solaris 8.

Answer 1

Bruce:
It sounds like (as you already note) failed to shutdown WLS, that is why the
.loc file was held and why the port is in use, WLS process was still
running. To see why it failed to shut down, I would examine the
weblogic.log, aslo the servers std out and err. Additionally taking a
thread dump (if possible) on the "it wont shut down" wls java process should
show (maybe unless the VM is hosed), where/what is hanging on/around. Do
you happen to have native code running with wls, say a type 2 JDBC driver?
Otherwise it sounds like a VM bug. But more data is needed to be sure.
Cheers
mbg
"Bruce Bryan" <[email protected]> wrote in message
news:3ef08499$[email protected]..
I was shutting down the WLS server using the console shutdown and itfailed to shutdown completely. I then attempted to use the kill command on
the process which usually works. This time I was unable to kill the process
without using the kill -9 command. When I attempted to bring the server
back up I got a failure to get a lock on the embedded ldap. I removed the
.loc file and came further up but was unable to get further than the
listener ports which were still locked to the old process. Do you know of
anything I can do the get the WLS server back up without rebooting my
Solaris server????
netstat -an shows the port is in use but the only process that is alloweduse that port is WLS.