Troubleshooting: DevOps Test Integrations and APIs Agent

You can use workarounds to common problems that you might encounter when you install and run the HCL DevOps Test Integrations and APIs Agent (Test Integrations and APIs Agent).

Table 1. Troubleshooting Test Integrations and APIs 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 Test Integrations and APIs Agent.

 Test Integrations and APIs 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.

Test Integrations and APIs Agent fails to start

The Agent workspace can get corrupted.

This problem occurs in any of the following conditions:
  • When JVM arguments for any application are added to Library Manager in the following instances:
    • For a new version of the application
    • For the second time to the same version of the application

    The cause can be that the same JVM arguments are already added when the application was configured the first time or for a previous version of the application.

  • When any of the JVM arguments added to Library Manager are invalid.

Try renaming the .integrationtester folder and restarting the Agent.

Perform any of the following actions:
  • When you add JVM arguments to Library Manager, you must change the dependent parameters or use different values for the parameters in the arguments.

    For example, you must set a different port from the port that is already set either in the previous version of the application or set during the previous installation of the application.

  • Enter valid JVM arguments to Library Manager.

Unix-like systems: program does nothing and exits

In Test Integrations and APIs Agent Installation Directory\configuration, check for log files with the file name format UTC timestamp.log (for example, 1253866725028.log). A new log file is created for each execution of the Test Integrations and APIs Agent and Library Manager (LibConfig).

Review the log files to locate the error. For information about using Library Manager, refer to Working with 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/libmawt.so: libXtst.so.6: 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: 
com.ghc.ghTester.commandline.PatternRunTargetException:
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 Test Integrations and APIs 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 Test Virtualization Control Panel to send the updated project to the Agent when the stub is next deployed.