Last updated on SEPTEMBER 06, 2016
Applies to:Oracle Scripting - Version 11.5.10 to 18.104.22.168 [Release 11.5]
Information in this document applies to any platform.
Checked for relevance on 04-March-2008
When a script is launched from TeleSales Agent Resonsibility/ eBusiness
Center form it does not free up its memory usage.
After a number of scripts runs the java console shows:
<<no stack trace available>>
Customer has to log out and back in again to continue running scripts.
Verified the issue by the following:
Turn on verbose GC output for the Jinitiator. Go to the control panel, and bring up control panel
for Jinitiator 22.214.171.124. To the Java Run time parameters field, add "-verbose:gc". This will
cause a DOS window to pop up when you start Forms. The JVM will output GC related messages to
this window. Specifically, at the end of every script transaction, a full GC will be called, and
you will see the final amount of consumed memory to the left of the arrow "->". This is the value
we care about, and which should not increase past a stable range.
After 10 Scripts runs:
[Full GC 38249K->31704K(55148K), 0.4362795 se
[GC 33752K->31777K(55148K), 0.0054694 secs]
The performance of opening the script is now starting to degrade.
After 10 more script runs:
[GC 63016K->61570K(88232K), 0.0156430 secs]
[Full GC 62458K->50646K(88232K), 0.9247404 secs]
After 10 more:
[GC 95067K->95010K(98048K), 0.0090277 secs]
[Full GC 96877K->83022K(98048K), 1.0363166 secs]
By now its taking 2 minutes to open the script.
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