SOACS Admin Server Is Not Starting. Logs Shows Error "java.net.BindException: Address already in use"
(Doc ID 2351519.1)
Last updated on OCTOBER 04, 2021
Applies to:SOA Suite Cloud Service - Version N/A and later
Information in this document applies to any platform.
Admin server in SOA CS environment is not starting. Logs shows the below port conflict errors.
<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.>
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