JVM Controller Logging
When logging is enabled, the JVM controller logs specific information to the log file.
The information are logged:
-
The values of the JVM parameters (maxsessions, classpath, and so on);
-
When a JVM controller starts and stops;
-
When a child JVM is spawned;
-
When an Forms runtime process starts a new connection, along with its process ID
This is useful for knowing which Forms runtime processes are connected to which JVM controller for diagnostics or administration;
-
When an Forms runtime process session ends and disconnects from the JVM.
The following section are included:
Specifying JVM Default Logging Properties
Use Fusion Middleware Control to manage the properties for JVM controller logging.
- In the JVM Configuration page, select the the JVM configuration section.
- For the logging parameter, enter a valid logging value, as described in Table -34.
- Click Apply.
Specifying the JVM Log Directory Location
You can specify the log file directory in the 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:
-
JVM controller, see Creating a New Configuration Section or Duplicating a Named Configuration.
-
Managing parameter, see Managing Parameters.
Accessing Log Files
When the log file exists, an icon is displayed in the Logfile column.
To access a log file:
-
Click the Log File link in the Logfile column that is available for that JVM controller.
The Log File page appears and displays the log information.
Deleting a Log File for a JVM Controller
Use Fusion Middleware Control to delete log files.
To delete a log file for a JVM controller:
Note:
If you delete a log file of a JVM that is running, the log file will be available again when the JVM is restarted. Logging is possible only when the JVM is restarted.