My Oracle Support Banner

Failure to Start WebCenter Spaces Managed Server Due To JOC Port Conflict, Error "Server failed to bind to the configured Admin port. The port may already be used by another process" (Doc ID 1615347.1)

Last updated on APRIL 13, 2018

Applies to:

Oracle WebCenter Portal - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

Unable to start WebCenter Spaces managed servers that are in a cluster. Other managed servers in the domain are able to start.

Errors in the startup logs look like this:

<Dec 12, 2012 2:59:16 PM EST> <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
<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>

Changes

Configured JOC for WebCenter Spaces Cluster.

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.