Error 'ODI-23035: Can not update the scheduling - This agent may not be running' With More Than One ODI Domain on a Single Machine

(Doc ID 2284201.1)

Last updated on JULY 27, 2017

Applies to:

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


There are two WebLogic Server (WLS) domains on the same machine, each having one managed server where a J2EE Agent is deployed. Each domain uses the same IP address, but different Oracle Data Integrator (ODI) repositories and ports.

For example,

Domain 1:
managed ODI_server1 port: 9103

Domain 2:
managed ODI_server2 port: 9109

Both domains are started for the first time, the agent test connection and the update scheduler are working on both.

Restart one WebLogic Domain (e.g. the second domain), log in to ODI Studio, and click the update schedule for the agent deployed on restarted domain. The following error is raised:

ODI-23035: Can not update the scheduling - This agent may not be running

oracle.odi.runtime.agent.invocation.InvocationException: http://[IP_Address]:9109/ Read timed out
  at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(
  at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invokeComputePlanning(
  at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invokeComputePlanning(
  at com.sunopsis.graphical.frame.edit.EditFrameSnpAgent$3.performAction(
  at oracle.odi.ui.framework.event.OdiActionListener.actionPerformed(
Caused by: Read timed out
  at Method)




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms