Discoverer Managed Server (WLS_DISCO) Fails to Start After Changing the Host Name
Last updated on APRIL 10, 2017
Applies to:Oracle Discoverer - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11g]
Information in this document applies to any platform.
On Oracle Discoverer 11g, after updating the host details to point to a new host name in following configuration files :
it is noticed that the Discoverer managed server (WLS_DISCO) fails to start.
The below entries are noticed in the wls_disco.log :
"<May 25, 2016 9:08:07 AM SGT> <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
<May 25, 2016 9:08:07 AM SGT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Server failed to bind to any usable port. See preceeding log message for details.>
<May 25, 2016 9:08:07 AM SGT> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address 172.16.3.22 might be incorrect or another process is using port 9001: java.net.BindException: Cannot assign requested address.>
<May 25, 2016 9:08:07 AM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<May 25, 2016 9:08:07 AM SGT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<May 25, 2016 9:08:07 AM SGT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN> "
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