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 NOVEMBER 03, 2020

Applies to:

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

Symptoms

NOTE: In the examples below, the names represent a fictitious sample for clarity. Any similarity to actual environments, past or present, is purely coincidental and not intended in any manner.

When starting an Oracle Data Integrator (ODI) agent, it may report an error about the address already being in use. 

The following examples show the error messages for different versions of ODI.

ODI 12c

The ODI agent fails to start with the error:

[2019-08-19T11:23:16.870-04:00] [odi] [ERROR] [] [oracle.odi.agent] java.rmi.server.ExportException: Port already in use: 20910; nested exception is: [[
java.net.BindException: Address already in use (Bind failed) oracle.odi.runtime.jmx.JMXPortException: java.rmi.server.ExportException: Port already in use: 20910; nested exception is:
java.net.BindException: Address already in use (Bind failed)
  at oracle.odi.runtime.jmx.JMXUtil.initRemoteJMXAccess(JMXUtil.java:166)
  at oracle.odi.Agent.startAgent(Agent.java:371)
  at oracle.odi.Agent.main(Agent.java:827)
Caused by: java.rmi.server.ExportException: Port already in use: 20910; nested exception is:
java.net.BindException: Address already in use (Bind failed)
  at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:346)
  ...
Caused by: java.net.BindException: Address already in use (Bind failed)
  at java.net.PlainSocketImpl.socketBind(Native Method)
  at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
  at java.net.ServerSocket.bind(ServerSocket.java:375)

ODI 11g

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 20910. Caused by: Address already in use (errno:226)
java.net.BindException: Address already in use (errno:226)
  at java.net.PlainSocketImpl.socketBind(Native Method)

ODI 10c

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: 20910
java.net.BindException: Address in use: JVM_Bind
  at java.net.PlainSocketImpl.socketBind(Native Method)

Alternate Errors

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 encountered an error: ODI-1434: Agent OracleDIAgent start failure: error while trying to use JMX Port 21910.
2017-09-23 13:40:00.987 ERROR java.rmi.server.ExportException: Port already in use: 21910; 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: 21910; nested exception is: java.net.BindException: Address already in use

or

java.io.IOException: ODI-1452: Agent OracleDIAgent cannot be started, http://<HOSTNAME>:20910/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)

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
 ODI 12c
 ODI 11g
 ODI 10c
 Alternate Errors
Cause
Solution
 Previous Agent
 Another Application


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