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

Last updated on AUGUST 14, 2017

Applies to:

Oracle Data Integrator - Version 12.1.3.0.0 and later
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:

"483664981@qtp-169916747-3151" #48690 prio=5 os_prio=0 tid=0x00007fa49001e000 nid=0x686e waiting for monitor entry [0x00007fa54c364000]
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)

"350987903@qtp-169916747-3170" #48841 prio=5 os_prio=0 tid=0x00007fa490041000 nid=0x2575 waiting for monitor entry [0x00007fa5577f9000]
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

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