Configuring and Managing Java Virtual Machines 10-17
When a user starts a salesApp application and it executes Java code, the Forms runtime process starts an in-process JVM in the same way the Java Importer works
without JVM pooling. When a second user starts the same application, the application will get their own in-process JVM, thus consuming more memory, as shown in
Figure 10–6 :
Figure 10–6 Multiple JVMs for multiple applications
10.9 JVM Controller Logging
When logging is enabled, the JVM controller logs certain information to the log file:
■
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. This section contains the following:
■
Section 10.9.1, Specifying JVM Default Logging Properties
■
Section 10.9.2, Specifying the JVM Log Directory Location
■
Section 10.9.3, Accessing Log Files
■
Section 10.9.4, Deleting a Log File for a JVM Controller
10.9.1 Specifying JVM Default Logging Properties
Use Fusion Middleware Control to manage the properties for JVM controller logging.
Application Server
Forms Runtime Process
“In-process” JVM
salesApp Client Forms Runtime
Process Forms Runtime
Process Forms Runtime
Process Forms Runtime
Process Forms Runtime
Process
“In-process” JVM
commonJVM
hrJVM
salesApp Client hrApp Client
hrApp Client ordersApp Client
ordersApp Client
10-18 Forms Services Deployment Guide
1. In the JVM Configuration page, select the the JVM configuration section.
2. For the Logging parameter, enter On or Off.
3. Click Apply.
10.9.2 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: 1.
Create a JVM controller. For more information, see Section 10.8.2.2, Creating a
New Configuration Section or
Section 10.8.2.4, Duplicating a Named Configuration
.
2. Add the Log Directory parameter. For more information, see
Section 10.8.3, Managing Parameters.
If you have duplicated a named configuration section that has Log Directory parameter defined in it, you can edit the existing parameter as given in the
Section 10.8.3, Managing Parameters.
3. Click Apply to save the changes.
The JVM Configuration page reappears.
10.9.3 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.
10.9.4 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: 1.
From the JVM Controllers page, select the the target JVM. 2.
Click Delete Logfile.
The Delete Confirmation dialog appears.
3. Click Delete.
The logfile is deleted and the JVM Controllers page reappears. 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.
Configuring and Managing Java Virtual Machines 10-19
10.10 Integrating Forms and Reports
