Very Frequent Full Garbage Collections Resulting in Poor Performance of ODI Agent
(Doc ID 1369755.1)
Last updated on OCTOBER 04, 2022
Applies to:
Oracle Data Integrator - Version 10.1.3.6.5 and laterInformation 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:HOSTNAME:PORT" daemon prio=10 tid=<THREAD_ID> nid=<ID> runnable [....]
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)
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
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
Symptoms |
Changes |
Cause |
Solution |
References |