SOACS Admin Server Is Not Starting. Logs Shows Error "java.net.BindException: Address already in use"

(Doc ID 2351519.1)

Last updated on JANUARY 25, 2018

Applies to:

SOA Suite Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Admin server in SOA CS environment is not starting. Logs shows the below port conflict errors.

<Jan 10, 2018, 4:50:26,720 PM UTC> <Error> <Server> <BEA-002606> <The server is unable to create a server socket for listening on channel "DefaultSecure[iiops]". The address <ip address> might be incorrect or another process is using port 9072: java.net.BindException: Address already in use>
<Jan 10, 2018, 4:50:26,721 PM UTC> <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured administrator port. The port may already be in use by another process.>
<Jan 10, 2018, 4:50:33,45 PM UTC> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: null>
<Jan 10, 2018, 4:50:33,47 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
<Jan 10, 2018, 4:50:33,47 PM UTC> <Notice> <WebLogicServer> <BEA-000382> <A critical service failed. The server will automatically transition to the ADMIN state.>
<Jan 10, 2018, 4:50:33,53 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN.>

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms