Logs overview

Rational® Performance Tester uses logs to store different types of information, which you can use to determine the reason for a test failure.

Rational® Performance Tester has the following logs:

Test logs

The test log contains a historical record of events that occurred during a test run or a schedule run, as well as the status of each verification point. The test log sets a verdict for each run as follows:

  • Pass indicates that all verification points matched or received the expected response and all the test steps successfully completed. For example, a response code verification point is set to PASS when the recorded response code is received during playback. If your test does not contain verification points, PASS means that all primary requests in the test were successful.
  • Fail indicates that at least one verification point did not match the expected response or that the expected response was not received or a Web UI step did not run successfully.
  • Error indicates one of the following results: a primary request was not successfully sent to the server, no response was received from the server for a primary request, or the primary request response was incomplete or could not be parsed.
  • The verdict is set to Inconclusive only if you provide custom code that defines a verdict of Inconclusive.
The verdict is rolled up from the child elements to the test level. For example, if a user group contains 25 virtual users, and five virtual users have failed verdicts, that user group has only one failed verdict, not five.

The test log file is stored in binary format with a .executiondlr file name extension in the project directory of your workspace. You can also view the test log in the user interface.

For more information about viewing test logs, see Viewing test logs.

Problem determination logs

You can set the level of information that is saved in the problem determination log during a run. By default, only warnings and severe errors are logged. Typically, you change this log level only when requested to do so by the Support person.

The problem determination logs contain internal information about the playback engine. These logs are particularly useful for debugging problems such as Kerberos authentication, SSL negotiation, and resource constraints on an agent. The log files are named CommonBaseEvents00.log and are located in the deployment directory. For example, if you play back a schedule on an agent and set C:\Agent as the deployment directory, the problem determination log files are in a directory similar to C:\Agent\deployment_root\<UserName>\A1E14699848784C00D2DEB73763646462\CommonBaseEvents00.log. If a large amount of log information is generated, multiple CommonBaseEvents files are created.

For more information about setting problem determination level, see Setting the problem determination level.

Agent logs

Look in %TEMP% directory for the majordomo.log file. This file contains information about the attempts to contact the workbench including information about any failures and the reason for the failures.

On the Microsoft Windows operating system, the %TEMP% directory is typically at %USERPROFILE%\AppData\Local\Temp.

If the majordomo service is configured to log in as Local System Account, then the %TEMP% directory is at %SystemRoot%\TEMP, typically C:\Windows\TEMP.

Error logs

If an error message is displayed when you run tests, try looking up the error message in the Performance testing error messages section of the online help. Only the most common error messages are listed. If no error message is displayed when you encounter a problem, open the error log by clicking Window > Show View > Error Log. If the workbench shuts down while running tests, restart the workbench and examine the error log. By default, warning and error messages are logged. You can increase the default logging level by clicking Window > Preferences > Logging. The log file is stored in the .metadata directory of your workspace. To avoid excessive logging, the Logging Level should be adjusted for individual Logger Names in the Loggers tab. For example, to get more information about a problem connecting with IBM® Engineering Test Management, increase the Logging Level for com.ibm.rational.test.lt.rqm.adapter Logger Name. For the licensing issue, adjust the level for com.ibm.rational.test.lt.licening Logger Name. When you no longer need the extra logging, use the Restore Default button in the Logging Preferences to reset all the levels to their recommended defaults.