Child pages
  • Troubleshooting
Skip to end of metadata
Go to start of metadata

This guide provides a collection of helpful hints and solutions for troubleshooting in loadIT if it's not working as you intend.

In general, before starting large scale distributed test executions, first execute the test plan locally with only one virtual user and reduced runtime and analyze the results in the view results tree listener.

For help about JMeter core components, you can also refer to the official JMeter documentation:

Some JMeter core components that are not needed in our case were hidden from the menu. They can be displayed by removing them from the not_in_menu property of the properties file. Some JMeter components were changed in their behavior, but these are explained in this documentation.

Port limitation in Windows:

As Windows limits the port numbers for outgoing connections, and limits the reuse-frequency, make sure to extend the possible ports by creating the following registry value:


DWORD MaxUserPort with value 65000 (decimal)/fde8 (hex).

Otherwise, there can be problems in case of high load tests. This should be done on the all the load test computers that create connections to the system under test (controller and agents).

Firewall blocking RMI traffic

Windows firewall

1. open network connections

2. select the network connection

3. right click and select properties

4. select advanced tab

5. uncheck internet connection firewall

Administrative privileges

loadIT can be run without administrative privileges. A message “WARNING: Could not open/create prefs root node…” in the console window may appear in this case and can safely be ignored.

HTTP Authentication Manager

The HTTP Authentication Manager can be used in the test plan.

Ramp UP Timer

A Ramp Up Timer is only allowed outside of a Runtime Controller and exactly one should be added at the very beginning of a test case.

Prefix for DB-Schema

If some database errors appear, please check if the db is using a prefix.

  • No labels