Automatic Diagnostic Repository Diagnostic Framework Components

13-8 Oracle Fusion Middleware Administrators Guide Figure 13–3 Incident Creation Generated by WLDF Watch Notification The steps represented in Figure 13–3 are: 1. The incident notification listener is initialized with component and application diagnostic rules. 2. Oracle Fusion Middleware Diagnostic Framework registers a JMX notification listener with WLDF. The listener listens for events from the WLDF Watch and Notification system. It only processes notifications of type oracle.dfw.wldfnotification. 3. Something in the system causes the configured WLDF watch to be triggered, causing a notification to be sent to the incident notification listener. The notification includes event information describing the data that caused the watch to trigger. 4. The Diagnostic Framework creates an incident in ADR. 5. The Diagnostic Framework executes the diagnostic dumps that are indicated by the diagnostic rules. 6. The Diagnostic Framework writes the dumps to ADR, in the directory created for the incident. 7. The Diagnostic Framework invokes the WLDF Diagnostic Image MBean requesting that a Diagnostic Image be created in ADR. 8. WLDF writes the Diagnostic Image to ADR.

13.3 Configuring the Diagnostic Framework

You can configure some settings for the Diagnostic Framework. In addition, you can configure an WLDF Watch and Notification to create an incident. The following topics describe how to configure the Diagnostic Framework: ■ Configuring Diagnostic Framework Settings ■ Configuring WLDF Watch and Notification for the Diagnostic Framework Managed Server WLDF Diagnostic Image MBean 2 3 Register 7 Write 8 Invoke Write Watch Notification Diagnostic Rules Incident Notification Listener Application Dump 1 Register 4 Component Dump ADR 5 Create Incident Execute 6 Execute 5 Notifiy Diagnosing Problems 13-9

13.3.1 Configuring Diagnostic Framework Settings

You can configure the following settings: ■ Enabling or disabling the detection of incidents through the log files ■ Enabling or disabling flood control and setting parameters for flood control You configure these settings by using the Diagnostic Framework MBean DiagnosticConfig. The following shows the MBeans ObjectName: oracle.dfw:type=oracle.dfw.jmx.DiagnosticsConfigMBean,name=DiagnosticsConfig Table 13–1 shows the parameters for the DiagnosticConfig MBean and a description of each parameter. Table 13–1 DiagnosticConfig MBean Parameters for Diagnostic Framework Parameter Description floodControlEnabled Enables or disables flood control. Specify true for enabled or false for disabled. The default is true. Note that flood control does not apply to manually created incidents. floodControlIncidentCount Sets the number of incidents with the same problem key that can be created within the time period, specified by floodControlIncidentTimeoutPeriod, before they are controlled by flood control. The default is 5. When flood control is enabled, if the number of incidents with the same problem key exceeds this count, no incidents are created, but the Diagnostic Framework writes a message at the WARNING level to the log file. floodControlIncidentTimeoutPeriod Sets the time period in which the number of incidents, as specified by floodControlIncidentCount, with the same Problem Key can be created before they are controlled by flood control. The default is 60 minutes. incidentCreationEnabled Enables or disables incident creation. Specify true for enabled or false for disabled. The default is true. logDetectionEnabled Enables or disables the detection of incidents through the log files. Specify true for enabled or false for disabled. The default is true. maxTotalIncidentSize Sets the maximum total size that is allocated for all incidents. When the limit is reached, the oldest incidents are purged until the space used by all incidents is less than the amount specified by this parameter. The default is 500 MB. The limit may be exceeded during the creation of an incident, but when the incident creation completes, the oldest incidents are purged. 13-10 Oracle Fusion Middleware Administrators Guide The following example shows how to configure these settings using the Fusion Middleware Control System MBean Browser: 1. From the target navigation pane, expand the farm, then WebLogic Domain. 2. Select the domain. 3. From the WebLogic Domain menu, choose System MBean Browser. The System MBean Browser page is displayed. 4. Expand Application Defined Beans, then oracle.dfw, then domain.domain_ name, then dfw.jmx.DiagnosticsConfigMBean. 5. Select one of the DiagnosticConfig entries. There is one DiagnosticConfig entry for each server. 6. In the Application Defined MBean pane, expand Show MBean Information to see the server name. The following shows the System MBean Browser page: reservedMemoryKB The amount of reserved memory that is released when OutOfMemoryError is detected. When the Diagnostic Framework starts, it allocates 512 KB of memory for its own private use. When the Diagnostic Framework detects that an OutOfMemoryError has occurred in the server, it frees that block of memory and proceeds to create the incident. The default is 512 KB. uncaughtExceptionDetectionEnabled Enables the Java-based uncaught exception handler. When enabled and an uncaught exception is detected, an incident is created. Specify true for enabled or false for disabled. The default is true. useExternalCommands Indicates whether external JVM commands should be used to perform thread dumps. Specify true for enabled or false for disabled. The default is true. Table 13–1 Cont. DiagnosticConfig MBean Parameters for Diagnostic Framework Parameter Description