Preventing Forms 11g Memory Jump after RUN_REPORT_OBJECT by Using a JVMCONTROLLER (JVM Pooling)
(Doc ID 1277681.1)
Last updated on DECEMBER 21, 2022
Applies to:
Oracle Reports Developer - Version 11.1.1.1.0 to 11.1.2.2.0 [Release 11g]Oracle Forms - Version 11.1.1.1.0 to 11.1.2.2.0 [Release 11g]
Information in this document applies to any platform.
Applies to Forms and Reports 11g
Goal
In 10g, the JVM pooling feature could only be used by the Java Importer. For this reason, methods such as the one mentioned in <NOTE 266073.1> were needed to reduce memory usage when using RUN_REPORT_OBJECT (RRO). However, in 11g, with JVM pooling enabled, Oracle Forms Services uses a shared JVM controller for Oracle Reports requests resulting in less overall memory usage. Here is a method for configuring a jvmcontroller to start when a form using RRO is called via a specific formsweb.cfg configuration section.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |