Databases Reference
In-Depth Information
Data. As you have learned in the
Troubleshooting the client-side issues
section,
you need to enable logging for
ActiveData.js
, and then inspect the log file
(for example, C:\temp\ActiveData<timestamp>.txt) at the client side.
Search the
MonitorMemoryLeaked
keyword in the
log
file, and you may
end up finding the following message:
ActiveData: MonitorMemoryLeaked: g_iMemoryLeakThresholdChars = 1048576this.m_iMemoryLeaked = 1049100
In this message there are two variables, which are explained as follows:
•
g_iMemoryLeakThresholdChars:
This variable represents a threshold
value defined in the
iActiveDataScriptsCleanupFactor
parameter
for Oracle BAM. The default value for
iAct-
iveDataScriptsCleanupFactor
is
1048576
(bytes), and you can view
and change this parameter in
BAMWebConfig.xml
, which is located in
the
<bam_domain_dir>/config/fmwconfig/servers/<serv-
er_name>/applications/oracle-bam_11.1.1/config
directory.
•
m_iMemoryLeaked:
This variable represents the total characters (in bytes)
of
all
ChangeList
payloads
that
have
been
processed
in
Act-
iveData.js
.
The
MonitorMemoryLeaked
message is written to the
log
file only when
m_iMemoryLeaked
reaches the threshold value (
1048576
bytes by default)
specified in the
iActiveDataScriptsCleanupFactor
parameter. In the
meantime,
ActiveData.js
attempts to free up memory consumed by IE,
close the previous connection, and then open a new connection to the BAM Re-
port Server.
