I'm struggling in performance testing. We are using e-Load for the same.
We have created script in e-Tester and trying to run that in e-Load. sometime it gives us "Driver Error 2014" , any idea why is it coming ?
Re: e-Load. problems.
yup, you are getting a timeout. Based on an old kbase article I saved to my "helpful stuff folder" The reason can be described as there are basically 4 components of the https requests that are made from the client to the server. Those components (these aren't the real names but I forget what they are really called) are Connect, Open, Send, and Read (there is actually 5 including the close connection, but once the connection is closed, there is no time associated with it). So, a standard eload 12002 or timeout error is produced when any one of these 4 requests times out after 120 seconds (default setting that can be changed). However, if one of these requests does not exceed the 120 second (default) timeout setting, BUT the sum of 2 or more DO exceed the total 120 seconds, then you will get the 2014 error. For all pratical purposes you can look at the 2014 error and the same as a client timeout. The page isn't coming back, you'll just be sitting there waiting 'cause you found a bottleneck.