SSL protocol error when attempting to connect with host - Error in Loadrunner

Error Description:

When we run the script in vugen, sometimes we get the SSL error in loadrunner, "SSL protocol error when attempting to connect with host". This error will not be resolved even when we try to run the script with different SSL versions in web_set_socket function.

Solution:

We need to enable the winlnet replay in Run Time Settings.

RTS >> Internet Protocol >> Preferences >> Advanced >> Use Winlnet replay instead of Sockets (Windows only)

Once this option is enables script will run without any SSL issues.

C Program to get the correlation parameter value of the last ordinal in loadrunner

Below C program is to fetch the value of the last ordinal in the correlation. We will be fetching the value using the total count of values (Ordinal count) which by default will be saved in a variable CorrelationParameterName_count. This program is highly useful when the ordinal value is varying for each iteration.

C Program:

char lastval[30];

web_reg_save_param("AcctName", "LB=\",\"accountName\":\"", "RB=\"", "ORD=All", LAST);


web_url("IZ7_JP4EHCS0N0KRC0QGT3G5TT",
"URL=https://XXXXXXXXXXXXXXXXXX/?jsondata=%7B%22provider%22%3A%22%22%7D",
"Resource=0",
"RecContentType=text/html",
"Referer=https://XXXXXXXXXXXXXXXXX/?isam_post_url_client_company_name=PTY_Banking",
"Snapshot=t6.inf",
"Mode=HTML",
LAST);


sprintf (lastval, "{AcctName_%s}", lr_eval_string("{AcctName_count}"));

lr_save_string( lr_eval_string(lastval) ,"AcctName_Last");

lr_message("Account Name last value is %s", lr_eval_string("{AcctName_Last}"));

How to create a JMX monitor in HP Sitescope

In this post I will detail about creating a JMX monitor in HP Sitescope to monitor the JVM's performance during our performance tests.

1. First the JMX port should be opened in the server whose performance has to be monitored. This will be usually done by the server admins or the operations team.
2. Example - 10.100.11.230:9003. Here 10.100.11.230 is the ip address of the server to be monitored and 9003 is the JMX port.
3. In the Sitescope Create Group --> Rt.click Create Monitor --> Add JMX Monitor
4. Under General Settings tab provide a relevant name to the monitor. Example JMX_HostName.
5. Under JMX Monitor Settings tab paste the JMX String service:jmx:rmi:///jndi/rmi://10.100.11.230:9003/jmxrmi in the field JMX URL.
6. Under the same tab click Get Counter and select the appropriate counters.
7. Under Monitor Run Settings tab mention the frequency at which this monitor has to be run.
8. Under Threshold Settings tab mention the threshold conditions to indicate the health of the monitor.
9. Once everything is set, Click Verify & Save button at the lower right bottom.

Thats it, your JMX monitor is ready 

Application to calculate the Pacing time, Users & TPS for Performance Tests

Today I am going to share an application which can be used to calculate the Pacing Time on the click of a button. This makes our Work Load Model calculations simpler, easier and quicker.

Input for Pacing calculation will be Transactions Per Second, Users & Think Time (Not Mandatory).

We can also calculate Users & Transactions Per Second using the same calculator.

Calculator Link