ODI 12c Agent Load Balancing: "java.net.SocketTimeoutException: Read timed out" Error Received and Causes the Scenario to be Re-executed Unexpectedly
(Doc ID 2488817.1)
Last updated on MAY 05, 2020
Applies to:Oracle Data Integrator - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
When Oracle Data Integrator (ODI) 12c Agent Load Balancing is configured, and the Slave Agent (which is executing a Scenario) is accidentally suspended...
... this causes:
- A "java.net.SocketTimeoutException: Read timed out" error to be signaled in the Master Agent log file:
== and ==
- The same Scenario to be re-executed by another Slave Agent.
This results in the same Scenario to be unexpectedly executed twice.
- Consider four standalone Agents on a same server, and configure the ODI Agent Load Balancing:
agent1 -- Master Agent
agent2 -- Slave Agent
agent3 -- Slave Agent
agent4 -- Slave Agent
- Execute a Scenario using "startcmd.cmd OdiStartScen" command against the Master Agent "agent1".
- The Scenario will be balanced to Slave Agent "agent2", and executed by "agent2".
- Suspend the Slave Agent "agent2", and observe the "java.net.SocketTimeoutException: Read timed out" message in the "odiagent.log" of Master Agent "agent1".
- Resume the Slave Agent "agent2", and observe that the Scenario execution completes without any error.
- Also observe that the same Scenario is re-executed unexpectedly by another of the Slave Agents ("agent3" or "agent4" in this example).
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