Solution:
Immediate resolution:
If you are sure that the test is complete and stopping the vuser forcefully won't affect your results then safest way is to do a Stop Now. In case that button is disabled then disconnect the Load Injector from the scenario. This will make the user to error-out. Re-connect the LG and re-collate the test results (in case it didn't collate properly).
There are 2 ways to change this value; one is to change the config file or using a function in your script.
Next thing you need to do is to restart the controller machine and register the controller dlls; this can be done by running the batch file "register_controller.bat"
placed at: "LoadRunner Install Dir\bin"
Log-off and re-login to the machine.
This case can get worsen if you are using CITRIX protocol and you manually tried to stop a vuser who was performing the below two functions at that time:
"ctrx_sync_on_bitmap_change" and "ctrx_sync_on_bitmap"
In case of you have large number of Vusers in your scenario then mention a limit on number of vusers that can stopped at given time also how you stop them. The setting for ramp-down limit is given in the LG properties:
For setting on how to stop the vusers:
In case of you have large number of Vusers in your scenario then mention a limit on number of vusers that can stopped at given time also how you stop them. The setting for ramp-down limit is given in the LG properties:
- Go to "Run-Time Quota" tab of LG details page and select the check-box for limiting the number of vusers that can be stopped and provide appropriate value in it.
For setting on how to stop the vusers:
- Open Tools -> Options in Controller and go to "Run-Time Settings" tab
- Select the appropriate option while stopping the vusers in the second option (depends on your scenario).
No comments:
Post a Comment