Tuesday, 15 January 2013

session - close connection in LoadRunner -



session - close connection in LoadRunner -

practical challenge: have lr script runs against app beingness mocked , not have logout button (yet). test runs fine stable response time 10 minutes, after response time peaks , server goes 99% memory usage , transactions start fail. suspect due script not terminate vusers after each run anf builds lot of running sessions against server wich not terminated. might wrong. anyays want programatically close each run after has competed business process. have reddish somewhere web_set_sockets_option ("shutdown_mode", "abrupt") used this, want sure function want , 'abrupt' means? there improve ways of closing sessions? clicking close browser during recording not result in beingness captured in script.

based on question assume you're using web/html protocol. agree core issue app's sessions should expire more elegantly , sooner. but, in order beyond while testing can seek this. isn't guarantee, has worked me in past when dealing similar situations. seek changing run-time settings script: run-time settings > browser > browser emulation

make sure have box checked "simulate new user on each iteration". can seek playing other settings here, clearing cache each iteration. cause new connection setting web page each iteration depending on server's session settings. again, isn't 100%, has worked me time time.

session loadrunner

No comments:

Post a Comment