Troubleshooting: HCL OneTest API Agent

You can use workarounds to common problems that you might encounter when you install and run the HCL OneTest™ API Agent.
Table 1. Troubleshooting HCL OneTest API Agent
Problem Description Solution
Project fails to open - duplicate items Each file within an Agent project has a unique identifier of the following format: editableResource createdTimestamp="1317292623890" createdUser="atester" id="- 44ea417a:132b496f2c1:-7e17 " type="test_resource"

This problem is caused by project files that are copied by using the operating system rather than copying within HCL OneTest API Agent.

HCL OneTest API Agent must always be used to copy objects.

The error message tells which files have the same ID's and the solution is to remove one of them and reopen the project.

HCL OneTest API Agent fails to start The Agent workspace can become corrupted. Try renaming the .integrationtester folder and restarting the Agent.
Unix-like systems: program does nothing and exits In HCL OneTest API Agent Installation Directory\configuration, check for log files with the filer name format UTC timestamp.log (for example, 1253866725028.log). A new log file is created for each execution of the HCL OneTest API Agent and Library Manager (LibConfig). Review the log files to locate the error. For information about using Library Manager, refer to Working with the Library Manager.
Linux systems: fail to start - java.lang.UnsatisfiedLinkError The following error occurs:
java.lang.UnsatisfiedLinkError: /home/root/jdk1.6.0_16/jre/lib/i386/xawt/ cannot open shared object file: No such file or directory
Install the libXtst package.

Contact your system administrator for assistance.

PatternRunTargetException occurs The following text is recorded in the log file:
no resources were found that matched the pattern:
The number at the end of the message, hashed above is the UUID of the resource.
The entry in the log file indicates that a resource is missing. Each file within an HCL OneTest API project is a resource and is identified by a UUID. The project files are XML files and the UUID of each can be found at XPath location: /*/@uuid. If the project is damaged, the project could contain a resource reference that has a UUID which is not fulfilled by any resource within the project. This can occur, for example, in a situation where the following tasks were done sequentially:
  1. A project is shared through a version control system.
  2. A new resource is added to a project locally.
  3. A resource containing the reference to the new resource is checked into the version control system, but the referenced resource itself is not added to the version control repository.
A problem would then occur when the stub was deployed from a computer other than the one which created the new resource.
  • Always publish stubs at a new version number.
  • Stop all stubs before republishing.
  • Unload the project from the agent manually.
    1. Go to the Agents and click the Magnifying Glass for the agent running the stub. You see a list of how many instances are running on each agent. Each instance corresponds to an execution of the RunTests binary. Where an instance has the appropriate domain, environment and version deployed, it will have an 'X' symbol.
    2. Click the 'X' symbol. Doing so will cause the running instance of the RunTests binary associated with the display to shutdown, and force HCL Quality Server to send the updated project to the Agent when the stub is next deployed.