Home
Troubleshooting and support
Learn how to troubleshoot some common issues with HCL Launch.
Logging
The server maintains logs for auditing and troubleshooting.
Determining the Java heap memory size
The Java heap is memory that contains objects used by Java programs. It contains objects that are currently in use, objects that are no longer needed, and free memory. Objects that are no longer needed are freed by the garbage collection process. The JVM heap size determines how often to run garbage collection and how long the garbage collection runs.

Troubleshooting and support
Learn how to troubleshoot some common issues with HCL Launch.
- Troubleshooting process overview
  Troubleshooting is the process of finding and eliminating the cause of a problem. When you have a problem with HCL Launch, the troubleshooting process begins as soon as you ask yourself what happened.
- Logging
  The server maintains logs for auditing and troubleshooting.
  - Viewing logs
    You can view logs from the Settings > System page.
  - Managing loggers
    You can add loggers to the root log and set their logging level to keep track of errors and some activities.
  - Configuring log rotation settings
    You can configure the rotation and increase the size of the main log file.
  - Managing the logs
    With appropriate permissions, you can add, edit, enable, and delete the default logs.
  - Determining the Java heap memory size
    The Java heap is memory that contains objects used by Java programs. It contains objects that are currently in use, objects that are no longer needed, and free memory. Objects that are no longer needed are freed by the garbage collection process. The JVM heap size determines how often to run garbage collection and how long the garbage collection runs.
- Troubleshooting the HCL Launch server and agents
  Troubleshooting information that is specific to the server and agents is provided here.

Determining the Java heap memory size

The Java heap is memory that contains objects used by Java programs. It contains objects that are currently in use, objects that are no longer needed, and free memory. Objects that are no longer needed are freed by the garbage collection process. The JVM heap size determines how often to run garbage collection and how long the garbage collection runs.

About this task

Tuning the heap size minimizes the amount of garbage collection processing. Insufficient Java heap space can result in out of memory errors or slow performance.

The JVM settings are specified in the set_env file which is in the ucd-server/bin directory. The JAVA_OPTS environment variable contains the following arguments related to heap size:

-Xms: Initial Java heap size.
-Xmx: Maximum Java heap size

For the Agent add -Xmx as the first line in the agent's conf/plugin-javaopts.conf file.