Preventing Forms 11g Memory Jump after RUN_REPORT_OBJECT by Using a JVMCONTROLLER (JVM Pooling)
Last updated on DECEMBER 28, 2017
Applies to:Oracle Reports Developer - Version 126.96.36.199.0 and later
Oracle Forms - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Applies to Forms and Reports 11g
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms