Skip Headers

Oracle® Application Server Forms Services Deployment Guide 10g Release 2 (10.1.2) B14032-03 |
| Library | Product | Contents | Index

Previous | Next |

# 7.6 JVM Controller Logging Management

When logging is enabled, the JVM controller logs certain information to the logfile:

- The values of the JVM parameters (maxsessions, classpath, etc.);

- When a JVM controller starts and stops;

- When a child JVM is spawned;

- When an Oracle Forms Runtime Process starts a new connection, along with its process ID

  This is useful for knowing which Oracle Forms Runtime Processes are connected to which JVM controller for diagnostics or administration;

- When an Oracle Forms Runtime Process session ends and disconnects from the JVM.

## 7.6.1 Enabling and Disabling Logging

This section contains the following:

- Section 7.6.1.1, "Specifying Default Logging Properties"

- Section 7.6.1.2, "Specifiying the Log File Directory Location"

- Section 7.6.1.3, "Accessing Log Files"

- Section 7.6.1.4, "Deleting a Log File for a JVM Controller"

### 7.6.1.1 Specifying Default Logging Properties

1. Select the default JVM controller.

2. Click Edit.

3. The Edit JVM Controller page appears.

4. From the logging dropdown box, select On or Off.

5. Click Apply.

   The Forms JVM Controllers page reappears.

### 7.6.1.2 Specifiying the Log File Directory Location

You can specify the log file directory when you create or edit a JVM controller. You can also specify the default JVM controller log file location for other JVM controllers to use.

To specify the log file directory location when creating or editing a JVM controller:

1. Click Create JVM Controller when creating a new controller, or select the radio button next to the target JVM controller.

   The Create New JVM Controller page appears or the Edit JVM Controller page appears.

2. Enter the following information for the JVM log file location:

   Log Directory

   Leave Log Directory empty to use the default log location for the default JVM controller. If any other directory is set, the log file cannot be viewed through Enterprise Manager.

3. Click Apply to create the JVM with these settings. The new JVM is automatically started.

   The Forms JVM Controllers page reappears.

### 7.6.1.3 Accessing Log Files

When logging is enabled for a JVM controller, a clickable icon in the Log File column will appear. When logging is disabled, the log file entry for that JVM controller is empty. See Section 7.6.1, "Enabling and Disabling Logging" for more information.

To access a log file:

- Click the Log File icon in the Log File column that is available for that JVM controller.

  The Log File page appears and provides the following information, as described in Table 7-7:

Table 7-7 Log File Page Information

Item | Description
--- | ---
Log File | Contains the name of the selected JVM controller
Component Name | Displays the name of the JVM controller
Component Type | Displays the application type
Modified | Displays the last time the log file was updated
Size | Displays the log file size in bytes
Log File Contents | Table that contains the most recent log entries. A maximum of 2000 lines is retrieved.
Log Text | Displays the latest entries in the log file

### 7.6.1.4 Deleting a Log File for a JVM Controller

To delete a log file for a JVM controller:

1. From the JVM Controllers page, select the radio button next to the target JVM.

2. Click Delete Logfile.

   The Delete Confirmation page appears.

3. Click Yes.

   The JVM Controllers page reappears.