Tracking Execution Flow by Analyzing an Operative Set

3-10 Configuring and Using the Diagnostics Framework for Oracle WebLogic Server

3.5.2.3 Tracking Execution Flow by Analyzing an Operative Set

The JFR graphical user interface in JRockit Mission Control allows you to analyze the run-time trail of system activity that occurs as the result of a particular event. In this example, the run-time trail is analyzed by first defining an operative set. An operative set is any set of events that you choose to work in JRockit Mission Control. In the example shown in this section, an operative set is created for the events that have the same execution context ID ECID attribute as the servlet invocation event selected in the Event Log table, shown in Figure 3–4 . The operative set is then analyzed to see the execution flow that resulted from that servlet invocation. Note that this operative set could be expanded to include events that match on different attributes as well; for example, events containing a specific SQL statement but not necessarily the same ECID. Figure 3–5 Operative Set Defined by Execution Context ID ECID This operative set is defined by right-clicking the desired event in the Event Log, and then selecting Operative Set Add matching ECID ecid. See Figure 3–6 . Figure 3–6 Defining an Operative Set by Matching ECID The operative set is then displayed by selecting Show Only Operative Set above the event log table, shown in Figure 3–7 . Note how the operative set is indicated in the range navigator. Using WLDF with Oracle JRockit Flight Recorder 3-11 Figure 3–7 Displaying an Operative Set The run-time trail of execution flow that results from the request that generated the servlet invocation event can be viewed by including additional event types. For example, Figure 3–8 shows the operative set when all WebLogic Server event types are added, using the Event Type Browser, and listing the events in chronological order. You can sort the events chronologically by selecting the Start Time column head. Figure 3–8 Adding all WebLogic Server Events to Operative Set In this example, note a portion of the execution flow shown in the Event Log: 1. The servlet URI is invoked. 2. The servlet uses an EJB, which requires access to the database. 3. A JDBC connection is obtained and a transaction is started.

3.5.2.4 Expanding the Operative Set and Viewing Correlated Diagnostic Data