E1: KER: KRM: How To Capture Diagnostics (CPU, memory, etc.) For A Running Call Object Kernel (Doc ID 2130576.1)

Last updated on MAY 30, 2017

Applies to:

JD Edwards EnterpriseOne Tools - Version 8.98 and later
Information in this document applies to any platform.

Goal

 The instructions in this document are used for the purpose of trouble-shooting any issue with a particular call object kernel that is running.

NOTE:  The instructions provided in this document are for capturing CPU, memory and some other diagnostic trace messages in the jdedebug log file for a specific call object kernel.  Capturing this diagnostic information for a particular call object kernel is not the same as enabling debug trace logging for the call object kernel.  See knowledge document 2116966.1 for instructions on how to enable debug trace logging for specific call object kernel.

Solution

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