oracle.odi.runtime.agent.invocation.InvocationException: ODI-1424: Agent host or port cannot be reached

oracle.odi.runtime.agent.invocation.InvocationException: ODI-1424: Agent host or port cannot be reached

oracle.odi.runtime.agent.invocation.InvocationException: ODI-1424: Agent host or port cannot be reached using http://localhost.localdomain.com:18502/oraclediagent.
at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.reThrowAgentErrorAsInvocation(RemoteRuntimeAgentInvoker.java:1301)
at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(RemoteRuntimeAgentInvoker.java:277)
at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invokeIsAlive(RemoteRuntimeAgentInvoker.java:428)
at oracle.odi.ui.action.SnpsPopupActionTestAgentHandler.actionPerformed(SnpsPopupActionTestAgentHandler.java:67)
at com.sunopsis.graphical.frame.edit.EditFrameSnpAgent.jButtonTestAgent_ActionPerformed(EditFrameSnpAgent.java:991)
at com.sunopsis.graphical.frame.edit.EditFrameSnpAgent.connEtoC...


bash-3.2$ ./agent.sh -NAME=OracleDIAgent -PORT=18502
NOTIFICATION ODI-1128 Agent OracleDIAgent is starting. Container: STANDALONE. Agent Version: 11.1.1.7.0 - 02/03/2013. Port: 18502. JMX Port: 19502.
NOTIFICATION ODI-1111 Agent OracleDIAgent started. Agent version: 11.1.1.7.0 - 02/03/2013. Port: 18502. JMX Port: 19502.
NOTIFICATION ODI-1136 Starting Schedulers on Agent OracleDIAgent.
 ERROR ODI-1131 Agent OracleDIAgent encountered an error: ODI-1540: Agent OracleDIAgent start failure: error while trying to use Http Port 18502. Caused by: Address already in use java.net.BindException: Address already in use


bash-3.2$ netstat|grep 18502

tcp 0 0 localhost:18502 localhost:18502 ESTABLISHED


Caused by: Address already in use java.net.BindException: Address already in use

This error indicates there is a port conflict & the port is already in use. 

In this case, there was a conflict with odi_server1 managed server & the agent. Issue resolved after shutting down odi_server1 managed server, starting the odi agent & then start odi_server1 again ...

BEA-002606 Unable to create a server socket for listening on channel "Default" java.net.BindException: Cannot assign requested address

BEA-002606 Unable to create a server socket for listening on channel "Default" java.net.BindException: Cannot assign requested address

In our SOA 11.1.1.5.0 non prod environments with WLS 10.3.5.0, recently there was an issue reported that someone was trying to start up weblogic server but was unable to start it up.

Error messages were as below:


<Feb 26, 2013 10:01:52 AM GMT> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address 141.143.2.43 might be incorrect or another process is using port 45901: java.net.BindException: Cannot assign requested address.>

Checked below:

1) ps ux to verify if there was any process running
2) netstat -an
3) Cleared tmp, cache and data directories of Admin and Managed servers and tried to bring up weblogic server but same issue.

Then later checked below:

1) /etc/hosts - IP address was changed
2) config.xml under $MW_HOME/user_projects/domains/domain_name/config/config.xml

config.xml was using old IP

3) Checked the nodemanager.properties file under $MW_HOME/wlserver_10.3/common/nodemanager

nodemanager.properties was using old IP.

Later we were informed that the IP addresses of the virtual machines had been changes.


Issue was resolved by using the new IP addresses in config.xml and nodemanager.properties.


Better solution is to use hostnames instead of IP addresses in the config files.