Known issues for load generators
This section describes troubleshooting and limitations for running Vusers on load generators machines.
Load generator not included with "All Generators"
Problem: I am adding a Vuser group to a scenario in percentage mode. When I click All Generators to add all the load generators to the scenario, the load generator called "localhost" is not added.
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.
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 <Installation directory>\Config\wlrun7.ini file. Under[General], add the following line:
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 System and protocol requirements.
For communication between the various LoadRunner Professional components (such as Controller and Load Generator, the MI Listener, etc.) you may need to specify your desired cipher. To do so, add a [SSLCipher] section to the config/m_agent_attribs.cfg file. Add the cipher name attribute using this syntax: "SSLCipherList=<cipher_string>". For details, see https://www.openssl.org/docs/man1.0.2/apps/ciphers.html.
LoadRunner Professional supports the latest versions of VMware ESX. 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.
You cannot run LoadRunner Professional projects created in Visual Studio (VB and C#) on remote load generators if they were launched by a limited, non-admin user.
ODBC scripts on Linux machines
When running ODBC scripts on RHEL 6, you may encounter the following replay error:
lrdb_open_connection: "SQLConnect", return-code=-1, native-error-code=0, SQLState=01000, SQLError=[unixODBC][Driver Manager]Can't open cursor lib 'libodbccr' : file not found"
Workaround: Create a libodbccr.so.1 soft link to libodbccr.so.2.0.0 using the following syntax:
n -s libodbccr.so.2.0.0 libodbccr.so.1
For details, see https://bugzilla.redhat.com/show_bug.cgi?id=719595.
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.
Scripts containing Japanese symbols may generate errors during replay or fail during replay, when running on Linux load generators set to a Japanese locale.