If you run tests and encounter problems, make sure that you have followed all the Performance testing tips.
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 .metadata directory of your workspace.
. 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 . The log file is stored in theIn addition to the online help, you can find workarounds or solutions to problems in the Rational Performance Testing forum on developerWorks®, and in the Support Knowledge Base technotes for Rational Performance Tester.
You might encounter some of these problems while performance testing:
If the workbench stops or locks up when you attempt
to start running tests, check that all the agent computers are running.
Restart the workbench computer and the agent computers. Make sure
that there is sufficient disk space on the workbench computer and
the agent computers. Check that there is network connectivity between
the workbench computer and agent computers. You can check the agent
status by clicking the icon. For Agent Controller, you can attempt to
share files between the workbench computer and agent computers. Click , and then add the agent computers as hosts, and click Test
Connection to test connectivity to the instances of the
Agent Controller that are running on the agent computers.
If a test runs but ends with errors, check that the workbench computer and agent computers meet the hardware and software requirements that are detailed in the installation guide. Pay close attention to the memory and disk space requirements. See Increasing memory allocation for more information on how to set the maximum heap size to avoid out-of-memory errors. Monitor processor and memory usage on the workbench and agent computers and watch for excessive processor use or excessive memory use by javaw.exe or java.exe processes. If error messages pertain to processes stopping unexpectedly, see this support article: http://www.ibm.com/support/docview.wss?uid=swg21395486.
Run tests with fewer virtual users that use the default schedule settings to determine whether the behavior is linked to the number of users. Examine the test log for error messages that the system under test generates. Run tests with a single virtual user and make sure that the system under test is not generating errors, before you attempt to run tests with a large number of users. If you encounter problems, restart the workbench and agent computers before attempting to run tests again.
If the workbench shuts down while running tests, search for file names that begin with javacore. The name of javacore files includes the date, time, and process ID. If you find a javacore file with a date, time, and process ID matching the workbench, open the file in a text editor. The cause of the failure is listed near the top of the javacore file.
If you can record tests successfully, but the expected behavior is not triggered in your application when you run tests, you might need to perform manual data correlation. Typically when additional data correlation is needed, the test log includes messages similar to this message:Unable to extract the value. To troubleshoot data correlation problems, try running tests using only one virtual user running on the workbench computer, and compare the playback to the recorded test to determine which responses from the system under test are unexpected. See Debugging HTTP tests to learn how to use the test log and the Protocol Data view to troubleshoot HTTP tests. To learn more about data correlation, see Correlating response and request data.