This topic provides information about how to troubleshoot
several problems with IBM® Rational® Performance Tester.
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 . 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 the .metadata directory
of your workspace.
In 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:
Connectivity problems between workbench and agent computers
If the workbench stops or locks up when you attempt to start running tests, it is important to
confirm that all the agent computers are running. Perform the following steps to confirm your
installation is properly configured:
- Confirm that there is sufficient disk space available on the workbench computer and the agent
computers.
- Restart the workbench computer.
- Verify the network connectivity between the workbench computer and agent computers. To confirm
the hostname in majordomo.config file can be DNS resolved on the agent machine, use a shell ping to
the workbench hostname. If the ping results fail use the IP address of the workbench instead.
- Confirm the server port number on the test workbench computer. Click . This is the port number that should be specified in majordomo.config file on the
agent machines.
- Restart the agent computers and verify the Majordomo process is running.
- On the agent machines, set the optional debug flag in the majordomo.config file. Set the value
equal to true; the default value is false. You do not have to restart the agent. Within about ten
seconds it should automatically pick up the changes to majordomo.config. Look in %temp% directory
for majordomo.log. In that file will be information about the attempts to contact the workbench
including information about any failures and the reason for the failures.
- You can check the agent status on the workbench computer by clicking the icon. For the 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.
Recording configuration problems
- No HTTP traffic is captured while recording
- See Recording reliable HTTP tests for
instructions on configuring your web browser. If you are attempting
to use Internet Explorer to record tests from a secure website, see Configuring Internet Explorer for recording from a secure web site.
Disable firewalls on the workbench computer and the agent computers.
- No traffic is captured while recording
- Ensure that the recorder type that you select matches the protocol
in use by the system under test. For example, do not attempt to use
the HTTP recorder if the system under test uses the Citrix protocol.
- No test is generated after recording
- When the test generator cannot create a test from the recorded
traffic, typically an error message is displayed or written to the
error log. Try looking up the error message in the Performance
testing error messages section of the online help. Error messages
might also be documented in technotes in the Support Knowledge Base
at http://www.ibm.com/software/awdtools/tester/performance/support/.
- Recorder controls are not available
- If you use a workspace from a different version of the product,
the recorder controls might not be available. Instead, the recorder
controls from the other version of the product are displayed. Click to reset the Performance Test or Service
Test perspective. Alternately, click to
select the wizard to use.
Problems running large tests or long-run tests
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.
Data correlation errors
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 ../../com.ibm.rational.test.lt.common.doc/topics/tdatacorrtop.html.
Common errors integrating with IBM Rational Quality Manager
All
modes of the adapter use the Eclipse error log. You can view the
log by opening the workbench and clicking . By default, warning and error messages are logged.
You can turn on more detailed logging for the adapter by clicking . The log component for
the adapter is named com.ibm.rational.test.lt.rqm.adapter.
If
you are running the adapter as a Windows service
or from the command line, you can view the adapter.log file
without opening the test workbench.
Problem |
Solution or cause |
Where do you look for errors or warnings? |
In the workbench, click . |
You do not see the adapter available for selection. |
- Verify that the Rational Quality Manager server
address that is provided to the adapter is correct. Provide the correct
address.
- Check the provided login and password. Provide the correct password.
|
The adapter continuously fails to connect to Rational Quality Manager. |
Make sure that the server is running. If necessary,
restart the server or check network connectivity. |
The adapter is displayed as red in the selection
dialog box. |
- The adapter is not communicating with the server.
- The adapter might already be in use.
|
You attempt to import a script from the adapter
but no scripts are found. |
- Make sure the project path that is entered in Rational Quality Manager is
a project under the workspace that is associated with the running
adapter. You have to enter only the project name. This is less error
prone than typing the complete project path, but either forms are
acceptable.
- If running from the command line or as a service, be certain the WORKSPACE_DIR environment
variable that is set in the adapter.config file
is the same path as seen in the select workspace dialog box when running
the test workbench. Be careful not to set the path to a project folder
under the workspace directory.
- Make sure that you are not using a workspace that contains a project
that was copied from a shared location. A workspace that contains
projects from shared locations cannot be used for projects that are
not shared.
|
The adapter is running from the command line
or as a service, and tests continue to fail. |
Run the adapter in GUI mode so that you can
see what happens when the test workbench runs the test script. |
Adapter Windows services
does not start. A error message states that the service failed to
start in a timely fashion. |
Ensure that the computer has .NET 2.0 or later.
This platform can be installed from the Windows Update Site or manually. For more
information on installing .NET, see http://support.microsoft.com/kb/923100. |
When testing shared assets, the execution fails
with and an IOException message is displayed. |
The most likely cause is that the Rational Quality Manager to
UNC shared location is not set up correctly.- From Rational Quality Manager,
ensure that you can access the UNC shared directory without being
prompted for a password. You might have to map a drive on Windows for the Rational Quality Manager system
to log into the UNC share.
- Ensure that you have defined the shared resource in Rational Quality Manager under .
- Ensure that the test-script points to a shared location that still
exists. If you have associated a Rational Quality Manager test
script with a shared location that has changed (for example if the
IP address has been reassigned) you might need to reassociate every
test script
- Ensure that the UNC shared directory that is specified in Rational Quality Manager points
to a project.
|
When testing shared assets, the execution fails
with a low level model error. |
Ensure that the adapter has the required protocol
extensions installed. The test assets located on the shared location
can only be run on an adapter workspace that supports those protocols. |
Service tests that were created in a previous
version of the product cannot be run. |
Upgrade every SOA asset to the latest version. |
The adapter cannot connect to the server, and
one of the following error messages is displayed:- Communications error with server
- Error occurred while registering the adapter
|
- When using Rational Quality Manager 3.0
or later, the server URL that is configured for the adapter must exactly
match the public URI of the Rational Quality Manager server.
The server public URI is available on the Rational Quality Manager administration
page. By default the administration page is at https://servername:9443/qm/admin.
- The adapter user must be a member of the Rational Quality Manager project
area. Open the project area administration page on the Rational Quality Manager server
to determine whether the adapter user is a member of the project area.
For Rational Quality Manager 3.0
and later, the adapter user must be a member in the test team member
role, not the test team contributor role. This error can also occur
if you have modified these roles from their defaults.
|