[Java SE] ODI Agent Is Consuming More Memory on the Server Than It Is Configured to Use
(Doc ID 2636986.1)
Last updated on FEBRUARY 20, 2020
Applies to:Java SE JDK and JRE - Version 8 and later
Information in this document applies to any platform.
System administrators were seeing reports of out of memory crashes with their Oracle Data Integrator (ODI) processes. Specifically with the agent, a stand-alone Java application that queues and processes integration jobs. Monitoring of the ODI agent process indicated the agent was using more than the configured amount of memory. All of the affected installations used Oracle's Java SE 8. The crashes took some time to manifest and did not happen in a predictable time frame.
The HotSpot crash log showed that the heap usage was below half of the allocated amount. The stack trace from the HotSpot crash log showed the crash happened when a class loader attempted to allocate more memory for itself. Monitoring with JConsole confirmed the heap was underutilized and that thread growth was modest and not growing.
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