Share this page

# Known issues for load generators

This section describes troubleshooting and limitations for running Vusers on load generators machines.

In this topic:

## Load generator not included with All Generators

When adding a Vuser group to a scenario in percentage mode, All Generators adds all the load generators apart from localhost.

Cause: By default, the load generator called "localhost" is defined as a Low Priority LG. Any load generator defined as a Low Priority LG is not included when clicking the All Generators button.

Resolution:

Do one of the following:

- Manually add the host that was not included

- Give "localhost" a different name, for example 127.0.0.1

- Shut down Controller and edit <installdir>\Config\wlrun7.ini file. Under [General], add the following line:

  HostWithLowPriority=

## Overloading of CPU

If you receive a warning indicating that the load generator machine has reached 80% of the CPU resources, make sure that your load generator machine conforms to the recommended Support Matrix.

## Virtual machines

The latest versions of VMware ESX are supported. However, running Vusers on virtual machines may adversely affect performance due to the sharing of physical resources.

## VB and C# projects

You cannot run VB and C# projects created with the Visual Studio add-ins on load generators with limited user permissions.

## Limited users

You cannot run OpenText Professional Performance Engineering projects created in Visual Studio (VB and C#) on remote load generators if they were launched by a limited, non-admin user.

## GUI Vusers

Windows Load Generator machines can only run one GUI Vuser at a time. To run multiple GUI Vusers in a load test, you need to open a terminal server session for each GUI Vuser.

## Non-English locales

Scripts containing Japanese symbols may generate errors during replay or fail during replay, when running on Linux load generators set to a Japanese locale.

## Automatic reconnection of load generators

If, during a load test, a load generator becomes disconnected from its network for a short period of time, Controller can automatically reconnect to the load generator and continue running the load test. However, you might experience the following issues when a load generator becomes disconnected:

- If the load generator is disconnected while the script is being transferred from Controller to the load generator, the load generator does not reconnect automatically. We recommend restarting the Controller if the connection is lost during script transfer.
- During the reconnection process, real-time data in Controller such as transactions and iterations might show lower than accurate values, because the values are not updated during reconnection. However, this data is not lost, and can be viewed in Analysis after the load test results are collated.

## Failure to add Linux load generators with IPv6

This section provides a solution if you are unable to add a Linux load generator machine using IPv6.

### On Windows

Locate the <installdir>\launch_service\dat folder and edit the following files:

- Locate the <installdir>\dat\br_lnch_server.cfg file, and set the following flag in the FireWall section: `FireWallServiceActive=1`

- Locate the <installdir>\config\m_agent_attribs.cfg file, and set the following flag in the Agent section: `IPv6=1`

### On Linux

- Locate the <installdir>/dat/br_lnch_server.cfg file, and set the following flag in the FireWall section: `FireWallServiceActive=1`

- Locate the <installdir>/config/.mercury/m_agent_attribs_<machine name>.cfg\ file, and set the following flag in the Agent section: `IPv6=1`

https://admhelp.microfocus.com Professional Performance Engineering,VuGen 8942
Tips to improve your search results... OpenText™ Professional Performance Engineering Help Center OpenText™ Professional Performance Engineering Help 26.1-26.3 All View Local Help Center View Online Help Center Version: