My Oracle Support Banner

OPMN Hangs / Times out - Log Shows "Address Already In Use", "Can't assign requested address", "Listener Bind failed" (Doc ID 444411.1)

Last updated on JULY 06, 2018

Applies to:

Oracle Fusion Middleware - Version 10.1.2.0.2 to 11.1.2.2.0 [Release AS10gR2 to Oracle11g]
Information in this document applies to any platform.

Symptoms

For 11g this may be more useful:

<Note 1303000.1> How to Troubleshoot Oracle Fusion Middleware 11g OPMN Issues?

 

Any attempt to start OracleAS 10g OPMN or OPMN managed components fails.

For example - the commands

opmnctl start
or
opmnctl startall

hang or timeout.

The ORACLE_HOME/opmn/logs/ons.log (OracleAS 10.1.2.x) or ORACLE_HOME/opmn/logs/opmn.log contains lines like

ONS server initiated


followed by error stacks like

BIND (Address already in use)
127.0.0.1:6199 - listener BIND failed
Listener thread -1275679824: 127.0.0.1:6199 (0x442) terminating
Local listener terminated

 

Error starting ORMI-Server. Unable to bind socket: Address already in use

 

BIND (Can't assign requested address)

 

java.net.ConnectException: Cannot assign requested

 

java.net.NoRouteToHostException: Cannot assign requested address

 

reserved_port() failed Cannot assign requested address

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
Cause
 Scenario A - BIND (Address already in use)
 Scenario B - Conflict with Oracle Server (RDBMS)
 Scenario C - Incorrect Network Configuration - BIND (Can't assign requested address)
Solution
 Scenario A
 Scenario B
 Scenario C
References

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