LMServer maintains an in-memory database. By default, this database holds up to 15 days worth of monitoring data. This database can fill up, causing LMServer to run out of memory.
ControlConsole is a Java utility which performs various logging and monitoring operations. ControlConsole accepts a number of command options, including the following options for freeing memory:
gc
Runs Java garbage collection.
dataunload <number of days of monitoring data to keep>
Releases monitoring data from memory that is older than the number of days you specify.
How to run the ControlConsole utility
1 Create the following environment variables:
AC_CONFIG_HOME
Location of the shared configuration directory for a cluster. If the system administrator created a folder for the shared configuration directory named config_cluster, and assuming the BIRT iHub installation folder is C:\Actuate\BIRTiHubVisualization, the default location for AC_CONFIG_HOME is:
Location of logs to which BIRT iHub processes write and System Console monitors. Assuming the BIRT iHub installation folder is C:\Actuate\BIRTiHubVisualization, the default location for AC_DATA_HOME is:
Location of the Java JDK and JRE. Assuming the BIRT iHub installation folder is C:\Actuate\BIRTiHubVisualization and the BIRT iHub install process installed a JDK, the default location for JAVA_HOME is:
C:\Actuate\BIRTiHubVisualization\modules\JDK64
2 Append the following value to the PATH environment variable:
%JAVA_HOME%\bin
3 Open a command prompt. Navigate to AC_SERVER_HOME\Jar. The lmsutility.jar file contains the ControlConsole utility. Run ControlConsole by executing the Java command, including the classpath of the ControlConsole utility, followed by:
-h <hostname> <command option>
For example, on a machine named urup, run ControlConsole with the help command option, which lists the ControlConsole command options:
java -classpath .;lmsutility.jar com.actuate.lmservice.utils.ControlConsole -h urup help
5 Release monitoring data from memory that is older than the number of days you specify by running ControlConsole with the dataunload <number of days of data to keep> command option. Listing 2‑5 shows running this command option to keep three days worth of monitoring data.
Listing 2‑5 Releasing monitoring data older than number of days you specify
6 View the amount of memory used and the amount of memory free by running ControlConsole with the memprofile command option. Listing 2‑6 shows running ControlConsole with this command option.
Listing 2‑6 Viewing the amount of memory used and amount of memory free
gc