Tuesday, 25 February 2014

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 ...



No comments:

Post a Comment