My Oracle Support Banner

Error "ODI-1434" or "ODI-1540: Agent MyAgent Start Failure Caused by: Address already in use" When starting ODI Agent (Doc ID 1575660.1)

Last updated on AUGUST 31, 2018

Applies to:

Oracle Data Integrator - Version 10.1.3.2.0 and later
Information in this document applies to any platform.

Symptoms

Given an Oracle Data Integrator (ODI) physical Agent called MyAgent, and MyPort - the Port number it should use (in accordance to the definition of MyAgent in the ODI Topology).

ODI 11g standalone Agent fails to start with error:

 ODI-1540: Agent MyAgent start failure

The ODI 11g Agent log is showing:

error while trying to use Http Port MyPort. Caused by: Address already in use (errno:226)
java.net.BindException: Address already in use (errno:226)
  at java.net.PlainSocketImpl.socketBind(Native Method)

The behavior is not specific to ODI 11g. Note however for ODI 10g, the error message might slightly differ if an older version of Java is used:

Port already in use: MyPort
java.net.BindException: Address in use: JVM_Bind
  at java.net.PlainSocketImpl.socketBind(Native Method)

In some cases, the agent will be unable to open up a companion port for JMX communication. This port number is generated by taking the base port and adding 1000 to it.

2017-09-23 13:40:00.984 ERROR ODI-1131 Agent OracleDIAgent_Collocated encountered an error: ODI-1434: Agent OracleDIAgent_Collocated start failure: error while trying to use JMX Port 27901.
2017-09-23 13:40:00.987 ERROR java.rmi.server.ExportException: Port already in use: 27901; nested exception is: java.net.BindException: Address already in use
2017-09-23 13:40:00.989 ERROR oracle.odi.runtime.jmx.JMXPortException: java.rmi.server.ExportException:Port already in use: 27901; nested exception is: java.net.BindException: Address already in use

or

java.io.IOException: ODI-1452: Agent OracleDIAgent1 cannot be started, http://Myhost:MyPort/oraclediagent is already in use by another agent.
  at oracle.odi.cam.plugin.nodemanager.OdiProcessHandler.isAlive(OdiProcessHandler.java:226)
  at oracle.odi.cam.plugin.nodemanager.OdiProcessHandler.start(OdiProcessHandler.java:97)
  at oracle.odi.cam.plugin.nodemanager.OdiProcessManagementPlugin$ProcessImpl.start(OdiProcessManagementPlugin.java:297)
  at weblogic.nodemanager.server.DecoratedSystemComponentManager$DecoratedProcess.start(DecoratedSystemComponentManager.java:129)
  at weblogic.nodemanager.server.ServerMonitor.startProcess(ServerMonitor.java:638)
  at weblogic.nodemanager.server.ServerMonitor.runMonitor(ServerMonitor.java:590)
  at weblogic.nodemanager.server.ServerMonitor.run(ServerMonitor.java:476)
  at java.lang.Thread.run(Thread.java:745)

Changes

 

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
Changes
Cause
Solution


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