New to this release


Connecting to HCL Quality Server with no Internet connection causes a long delay in loading pages. This problem is because content cannot be downloaded from


When an engine is started by an agent, the agent log contains messages about unrecognized options similar to: 

[RunTests/instance1 (0)]: Unrecognized option: -domain 
[RunTests/instance1 (0)]: Unrecognized option: -instanceUUID 
[RunTests/instance1 (0)]: Unrecognized option: -version 
[RunTests/instance1 (0)]: Unrecognized option: -projectString 

These messages are output erroneously and can be ignored. 


The set of garbage collection policies available when configuring JVM options for an agent within HCL Quality Server includes an invalid option "subpools".


After HCL Quality Server is upgraded, invalid error messages that relate to upgrading database entities show in HCL Quality Server logs.


Synchronizing a WSDL document fails after editing its URL value in the Schema library.


When running a Stub in HCL OneTest API which has an environment task, when the environment task completes, the stub is started but is not shown in the Task Monitor.


The sending of HTTP Messages with payloads do not have their Content Type headers created by default.


Installation Manager offers an option to switch to 32-bit architecture. This option is invalid and should be ignored. Only 64-bit architectures are supported.


After you install HCL Quality Server on Windows 10 fix version 1809+ and start the HCL Quality Server service, it shows as running, but after 30 seconds or so, refreshing the Windows services panel removes the running status and you cannot choose to stop the service. HCL Quality Server is actually running and you have to use the command line to stop it. 

This problem is a change in Windows behavior as described at

To workaround the problem, change 

start /b  to  start /min /b  in <HCL Quality Server_install_dir>\bin\server.bat


If an agent is started from a directory other than the installation directory, logs for engines started by the agent are not created. The message similar to the following message is output:

"Unable to read logging configuration due to exception: /opt/IBM/ (No such file or directory)"


The Status column of the Scheduling page for HCL Quality Server shows a running scheduled test as scheduled.


When running under a non-IBM JRE, synchronization with IBM Integration Bus over a secure connection is not possible due to an onward dependency in the IBM libraries.

Previous known issues that still apply


If a stub event passes its guard condition, only single values are saved to tags on repeating elements. With no guard condition, tags are correctly populated with multiple values.


When using Git source control and a database is updated from a compare with a remote Git repository, the decorator icon in the Test Factory tree is not updated to show the correct Git status.


Using Git integration in HCL OneTest API increases the memory consumption of the tool.


Proxy recording of AMQP messages on operations or an Ad Hoc monitor targets a proxy queue, rather than an exchange + a routing key, to consume all the messages that are sent by the user application to the proxy queue (denoted by combining the actual queue name with the Queue Suffix defined into the RabbitMQ Transport). As a result when the configuration of the operation or the Ad Hoc monitor does not express a Queue, for example, an empty exchange and the name of the queue as the routing key, the start of the recording is prevented with an exception and a message that indicates the expected configuration.


Maven pom files generated from an earlier version of HCL OneTest API do not run with HCL OneTest API 9.2.1 or later. To workaround this problem, for pom files generated from HCL OneTest API or later, run the Maven command 'mvn versions:update-property -Dproperty=it-plugin-version -f <name of pom file>' to discover the new version from HCL Quality Server and update the version value. Otherwise, for pom files generated from earlier versions of HCL OneTest API, generate a new pom file or edit the earlier pom file by replacing the version number in the old pom file (for example, 1.911.1 for HCL Quality Server 9.1.1) with the version number from HCL Quality Server 9.2.1 (for example, 1.921.0).


When you first start an information center, you might see an error that indicates Eclipse is unable to acquire a PluginConverter service. You can safely ignore the "Unable to acquire PluginConverter service during generation for:" error messages. 
Stop the information center and then restart it.


When Domain Level Security is enabled and a security token is created for the HCL Quality Server system administrator, this security token does not allow Agent and Proxy processes to register with HCL Quality Server. To workaround this issue, add the HCL Quality Server system administrator as a "user" of one of your domains.


In the 9.2.1 Environments dashboard, there can be only one instance of a running stub for each stub type that is published into a specific environment in a domain. The option to clone a stub from the Environments page available in 9.2 release is removed in 9.2.1 release.


In HCL Quality Server, the Infrastructure Dashboard displays the identifier for agents and proxies in the Identity column that was configured in the agent or proxy configuration file. If not configured, the Identity column displays the host name of the computer that is running the agent or proxy.


Newly created transient environments, as used by the UrbanCode Deploy plug-in, currently do not include the new managed stub instances.


When you work with the HCL Quality Server dashboards while HCL Quality Server security is enabled, when the browser session times out, you are redirected to the Login page. After you log back in, you are redirected to the HCL Quality Server landing page, instead of the page listed in your browser URL.


The Engine identity in the HCL Quality Server Infrastructure dashboard displays the project name and version which may be duplicated if that project is deployed to more than one engine simultaneously.


In the stub's Activity tab in HCL Quality Server Environments Dashboard, the 'User' field may sometimes display "Unknown user" instead of a system account.


In some circumstances, from the routing rules that are shown on the Network dashboard, it is not possible to determine the agent on which a virtual service is running.


The Integration Tester Results plugin in Jenkins cannot display results because the plug-in cannot find the results link.


Before a Mac OS user installs Integration Tester, a Java JDK must be installed first from this web site: The latest JDK version of Java 8 is: jdk-8u161-macosx-x64.dmg


Topology discovery for WebSphere MQ is not available for WebSphere MQ on z/OS.


When you use the Maven plug-in, if resources other than tests and stubs are run (specifically suites or performance tests), then the environment attribute in the pom.xml is ignored. To work around this problem, add an environment argument (-environment arg) in the pom.xml. If you do not use this workaround, then the result is either an UnsupportedOperationException being thrown, or if the project was opened on the workstation before, the most recently used environment is used instead.


In 9.1.1 the protocol that is used to communicate with HCL Quality Server changed to be HTTPS (by default). When recording messages in Recording Studio often these messages are sent direct from the agent/proxy to IntegrationTester. The transport that is used is agent/proxy specific and not usually encrypted.


In 9.1.1, HCL Quality Server and Integration Tester, by default, use an SSL certificate and private key shorter than 2048 bits. As such they are not in compliance with industry standards set by the Certification Authority/Browser (CA/B) Forum. HCL Quality Server can be configured to use the compliant 2048 versions by changing the keystore path in the server.custom.xml file to the available 2048 bit greenhat2048.jks keystore. In Integration Tester, the compliant Inbuilt Certificate Authority can be selected in the Project Settings.


The DB2 for z/OS intercept cannot use HTTPS to communicate with HCL Quality Server.

For a complete list of previous known issues that still apply before 65808, see the 9.5 release documentation known issues list.