Very Frequent Full Garbage Collections Resulting In Poor Performance Of ODI Standalone Agent

(Doc ID 1369755.1)

Last updated on MAY 12, 2017

Applies to:

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

Symptoms

When consulting the Oracle Data Integrator (ODI) Agent Thread dump, it shows that the Agent is forcing the JVM to execute a garbage collection.

Here is a sample snippet from the Thread dump:

"DwgCmdExecutionThread:UXPRD150:8016" daemon prio=10 tid=0x08525400 nid=0x6d95 runnable [0x8c7ba000..0x8c7bae20]
java.lang.Thread.State: RUNNABLE
  at java.lang.Runtime.gc(Native Method)
  at java.lang.System.gc(System.java:928)
  at com.sunopsis.dwg.cmd.DwgCmd.A(DwgCmd.java)
  at com.sunopsis.dwg.cmd.DwgCmd.run(DwgCmd.java)
  at java.lang.Thread.run(Thread.java:619)

Changes

 

Cause

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