This Vuser already started a transaction with the same name issue in Performance Center

It's most likely because we started two transactions with the same name and didn't finish the first before starting the second. If an issue occurs when using the TruClient logic to start/end transactions, the open transactions will fail. Every object or transaction that is open must be closed.

How to Change TLS Version in Jmeter? TLS Version Jmeter settings

If you haven't altered the default settings, JMeter should be using the TLS protocol in general, and TLSv1.2 specifically. If this doesn't match your payment gateway pr your application settings, change https.socket.protocols to match what your application requires.

You can add the following lines to the log4j2.xml file to get debugging output for SSL and network things.

<Logger name="org.apache.jmeter.util.HttpSSLProtocolSocketFactory" level="debug" />
<Logger name="org.apache.jmeter.util.JsseSSLManager" level="debug" />
<Logger name="org.apache.http" level="debug" />
<Logger name="org.apache.http.wire" level="debug" />

and change the below line in system.properties file:

javax.net.debug=all

Note: Must and should restart your Jmeter to update the above changes

Reasons for High response times - Page Performance

Basically it all relies on how you put up your scenario.So having a high response time could be your application as well, but again, you must examine your scenario settings before drawing any conclusions about high response time.

The logs that were recorded during your test run are known as execution logs.We shouldn't keep the login component of the script in the Action section because it doesn't appear to be a realistic scenario.
Consider whether a real-world user (Customer) logs in and out as frequently as you're having your app do in your scenario.My recommendation is to keep login in the init part and logout in the end section of the scripts.However, I'm still thinking about your scenario.


1. As test results, you must have a.lrr file.(If the test was run in the controller)

2. Use the Analysis LR component to open the.lrr file.Allow it to open the entire data set.
The data creation component is located at the bottom of the analysis component.

3. Once you've gotten 100 percent of your data, you can move on to the next step.Open the graph of Average Response Time.

4. Right-click on the graph and choose Merge Graph > Running Vuser Graph.You'll be able to run vuser as a result of this.

4. Right-click on the graph and choose Merge Graph > Running Vuser Graph.This will combine the graphs of the running vuser and the average response time into a single graph.

5. Using this graph, you may determine when the user load login procedure began to take longer.
Once you've identified the point at which the login transaction begins to take longer, write down the time and what the user load is at that exact moment.

6. Now open other graphs such as CPU utilization and Memory utilization (Committed Bytes/ Available MB) and verify their consumption levels. If you notice utilization above 90%, note down the user load and the time when your server starts consuming above 90%.

With this information, report it to the development/application team.This will be beneficial to them.Request that they keep an eye on the application server from the back end as you execute the load test.They will have a better understanding of the fundamental problem as a result of this.

Error:Vuser type "WS_SOAP" specified in xxx. use cannot be found

During your load test,some times you may see this type of errors. The reason for the issue is Linux Load Generator. 

Web Services protocol will not work with a Linux as a Load Generator only with Windows OS. Change the LG to windows and then it will execute successfully. 

Initialization has failed. Contact your system administrator. For details, see the loader log file

To resolve this issue,follow the below steps.

1.Close all Internet Explorer windows

2. Run the uninstall utility tool: https://marketplace.microfocus.com/appdelivery/content/alm-client-cleanup-add-in

3. Please navigate to the %Temp% folder. Once in the “Temp” folder delete the “TD_80” subfolder. This is better known as the QC Cache. Like “Temporary Internet Files” this can be safely deleted. It will be recreated upon the next logon to Quality Center.

4. Use right click on Internet Explorer and select “Run as Administrator”

5. In the toolbar select Tools -> Internet Options

6. In the window that opened navigate to tab General

7. Under the section Browsing Settings click the History Button

8. In the window that opened click on the button View Files button

9. Delete all Temporally Internet Files

10. Temporarily disable UAC (User Account Control) and DEP (Data Execution Protection) settings. ALM has many known issues with these settings.

11. Reboot your client machine

12. Right click on Internet Explorer and select “Run as Administrator”

13. Open Quality Center main page (this will start to download the client components from the server)

14. Click on "Tools" page

15. Click on "HP ALM Client Registration"

16. Click on "Register HP ALM”

17. Click on "Tools" page

18. Click on “HP ALM Connectivity”.

19. Download the connectivity add in and install it on the client machine.Now go back and check,that will surely work.