Troubleshooting: HCL Quality Server

You can use workarounds to common problems that you might encounter when you use HCL Quality Server.
Table 1. HCL Quality Server problems and workarounds
Problem Solution

Issues with startup, web server, unrecognized registration or other messages from agents or proxies while working on the HCL Quality Server.

Analyze the log files for investigating the issues. The log files are located in the HCL Quality Server installation directory\logs and HCL Quality Server installation directory\logs\additional
After upgrading to the latest version, you might have issues if you have not closed the HCL Quality Server session in the web browser. Refresh the session in the browser by using the Shift+F5 keys or close the browser tab and then log in to HCL Quality Server
After installing the latest version, you want to change the runtime language. HCL Quality Server typically detects the language of the browser configuration and displays that language. However, if that is not the case, you can modify the URL that is used to access the HCL Quality Server by adding the language that you want to use. For example, if you want to display French, you use the following code:
https://mydefaultServer:5443/RTCP/?locale=fr 

For a complete list of language codes, see Internet Assigned Numbers Authority (IANA) Language Subtag Registry. .

After you upgrade to the latest version, nothing that is configured to communicate with HCL Quality Server is able to connect to it. It does not load in a browser.

The following log message appears in the HCL Quality Server log files:

[ERROR] CWWKT0022E: The configured host 0.0.0.0 for HTTP endpoint defaultHttpEndpoint could not be resolved. The endpoint has been disabled.

Edit the RTCP/config/server.custom.xml file to do one of the following:
  • Replace 0.0.0.0 with *.
  • Remove the host attribute to use the default.
  • Remove the entire httpEndpoint element to use the default for all its attributes.

The HCL Quality Server process exits with Java heap space errors in its log.

HCL Quality Server is no longer accessible. The process ran out of memory and crashed.

The HCL Quality Server logs/console.log file contains the following errors:

java.lang.OutOfMemoryError
Java heap space

A Java™ dump output follows.

Java ran out of memory because Java has a fixed upper limit.

The HCL Quality Server start scripts do not explicitly set the Java memory size limit so it is using a default value that is calculated by using the system memory.

Typically the scripts allocate 512 MB.

This problem can be caused by any of the following tasks:
  • Publishing large projects
  • Deploying large projects
  • Viewing large reports in the HCL Quality Server web interface, for example those of HCL OneTest™ Performance
Check the contents of the console.log. For Windows systems the log file is typically in C:\Program Files\HCL\HCLProducts\QualityServer\logs

For non Windows systems the log file is typically in /opt/HCL/HCLProducts/QualityServer/log

Check what the Java memory size limit is as follows:

  1. Open a command window on the HCL Quality Server server.
  2. Go to the jre/bin folder of the HCL Quality Server installation.
  3. Run java -verbose:sizes -version

    Look for the value of -Xmx, for example:

    -Xmx512M memory maximum

    On non Windows systems, run ./java -verbose:sizes -version

Increase the memory allocation.

  1. Shut down HCL Quality Server.
  2. Edit <HCL Quality Server installation>/setenv.bat or setenv.sh depending on the operating system. Add the setting:
    JVM_ARGS=-Xmx1024M -Djava.net.preferIPv4Stack=true ...
  3. Restart HCL Quality Server.
  4. Check and reconfigure this value after a version update as the change is overwritten.
Installation Manager supports rolling back the HCL Quality Server installation directory, but not the workspace directory. If you roll back the HCL Quality Server installation directory and do not delete the workspace directory, HCL Quality Server fails to start.
To roll back HCL Quality Server and not reuse the workspace directory:
  1. Uninstall the current version of the installation and delete the workspace directory while uninstalling the installation.
  2. Install the older version of the installation with a new workspace directory.
To roll back HCL Quality Server and reuse the workspace directory:
  1. Uninstall the current version of the installation and do not delete the workspace directory while uninstalling the installation.
  2. Install the older version of the installation.
  3. Configure the workspace directory to work with the older version of the installation. For more information about reusing the workspace, see HCL Quality Server upgrade information and requirements.
Note: Starting from V9.2.1 onwards, when you roll back a HCL Quality Server version, the workspace cannot be reused and must be reinstalled.
Feedback