IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual page 154

HEAPDUMPs and JAVACore files, an out-of-memory condition, when you are
logged on. Make the following adjustments to correct this problem:
v Increase the Java heap size settings. Set the minimum heap size to 128 MB. Set
v When memory requests by the Tivoli Enterprise Portal cannot be satisfied from
v If you observe symptoms of heap memory exhaustion after changing the heap
v Make sure the client workstation has enough memory to handle the maximum
v Set the Java Plug-in cache to an unlimited size to avoid performance problems
v If you have just upgraded to a new release or fix pack, clear the plug-in cache to
Complete the following steps to adjust the Java Plug-in settings:
Procedure
1. Open the Windows Control Panel.
2. Double-click IBM Control Panel for Java(TM) to display the Java(TM) Control
3. From the Java(TM) tab:
4. Click OK.
5. From the General tab complete the following steps to clear the browser cache:
6. Click OK in the Java(TM) Control Panel.
136
IBM Tivoli Monitoring: Troubleshooting Guide
the maximum heap size to 256 MB. If you continue to experience problems,
increase the maximum setting in increments of 64 MB until the symptoms
disappear.
Java heap storage, the JVM performs garbage collection to reclaim free memory.
If the Java heap size settings are too small, the amount of time it takes to
perform garbage collection becomes excessive, resulting in high CPU utilization
and poor response time. In some cases, Java HEAPDUMPS and JAVACore files
are placed on user desktops, indicating an out-of-memory condition. Increasing
the Java heap size parameters over the default values helps you avoid these
problems.
size settings to the suggested values, increase the maximum setting in
increments of 64 MB until the symptoms disappear.
heap size. To determine if the client workstation has sufficient memory, observe
the available physical memory (as shown on the Windows Task Manager
Performance tab) when the workstation is not running the Tivoli Enterprise
Portal client, but is running any other applications that need to run concurrently
with the portal client. Verify that the client workstation has enough available
physical memory to hold the entire maximum Java heap size for the Tivoli
Enterprise Portal plus another 150 MB. The additional 150 MB provides an
allowance for non-Java heap storage for the Tivoli Enterprise Portal and extra
available memory for use by the operating system.
due to insufficient cache space for Tivoli Enterprise Portal JAR files.
remove old versions of the Tivoli Enterprise Portal JAR files.
Panel.
a. Click View.
b. Double-click on the Java Runtime Parameters field and enter: -Xms128m
-Xmx256m .
a. Click Delete Files...
b. Check the box labeled Downloaded Applets.
c. Click OK.