"ODI-1274: Agent Exception" And "java.net.SocketException: Connection reset" Captured When Executing An ODI 11g Scenario On a J2EE Agent Set Up On a Load Balanced Weblogic Server Configuration

(Doc ID 1458724.1)

Last updated on FEBRUARY 08, 2017

Applies to:

Oracle Data Integrator - Version and later
Information in this document applies to any platform.
***Checked for relevance on 07-Jan-2014***


An Oracle Data Integrator (ODI) Scenario started via "startcmd.bat/sh" script errors after five minutes of execution throwing error:

Caused by: java.net.SocketException: Connection reset

 A further error is captured in the J2EE Agent log file:

ODI-1274: Agent Exception
Caused by: javax.xml.bind.MarshalException
- with linked exception:
[java.net.SocketException: Broken pipe]
   at oracle.odi.runtime.agent.servlet.AgentServlet.processRequest(AgentServlet.java:490)
   at oracle.odi.runtime.agent.servlet.AgentServlet.doPost(AgentServlet.java:394)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
   at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)

... and finally a third error is captured in the Oracle Listener log:

ORA-12170: TNS:Connect timeout occurred

28-APR-12 01.53  PING[TST]: Heartbeat failed to connect to standby 'XYZ'. Error is 12170.
28-APR-12 01.56  Fatal NI connect error 12170.



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