Failure to Start WebLogic Managed Server with Error "Server failed to bind to the configured Admin port. The port may already be used by another process."
(Doc ID 1513052.1)
Last updated on JUNE 12, 2018
Applies to:Oracle Weblogic Server - Version 9.2 and later
Information in this document applies to any platform.
There were two failures on two different systems. On one system, the WLS managed server failed to start. On another system, the managed server started, but Oracle HTTP Server would not start.
On the first system, this was seen in the startup logs:
<Dec 12, 2012 2:59:16 PM EST> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address aa.bb.ccc.ddd might be incorrect or another process is using port 80: java.net.BindException: Permission denied.>
<Dec 12, 2012 2:59:16 PM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Server failed to bind to any usable port. See preceding log message for details.>
<Dec 12, 2012 2:59:16 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Dec 12, 2012 2:59:16 PM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Dec 12, 2012 2:59:16 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document