My Oracle Support Banner

ODI 12.1.3 Agent Consuming Maximum CPU and Not Answering to Requests for New Executions (Doc ID 2294299.1)

Last updated on FEBRUARY 11, 2019

Applies to:

Oracle Data Integrator - Version 12.1.3.0.0 to 12.1.3.0.1 [Release 12c]
Information in this document applies to any platform.

Symptoms

In Oracle Data Integrator (ODI) 12.1.3, the J2EE Agent is taking up all of the CPU, and new jobs sent to the Agent hang and are not executed. 

The stack dump contains BLOCKED messages like the following:

"<ID>@<STRING>" #<ID> prio=5 os_prio=0 tid=<TID> nid=<NID> waiting for monitor entry [<VALUE>]
java.lang.Thread.State: BLOCKED (on object monitor)
at com.sunopsis.dwg.dbobj.SnpScen.getObjectLst(SnpScen.java:215)
- waiting to lock <0x00000006c1dfdcd0> (a java.lang.Class for com.sunopsis.dwg.dbobj.SnpScen)

"<ID>@<STRING>" #<ID> prio=5 os_prio=0 tid=<TID> nid=<NID> waiting for monitor entry [<VALUE>]
java.lang.Thread.State: BLOCKED (on object monitor)
at com.sunopsis.dwg.dbobj.SnpUser.getUserByName(SnpUser.java:109)
- waiting to lock <0x00000006c12cccd0> (a java.lang.Class for com.sunopsis.dwg.dbobj.SnpUser)

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.