Quantcast
Channel: LoadRunner Practitioners Forum topics
Viewing all articles
Browse latest Browse all 3978

user abort strategy

$
0
0

I'm using LR11.0

I have a senario with real-world shedule, with the duration set to 30 minutes.

the document says that when time comes, loadrunner will first end the iteration then go to action_end, because I set "When stopping Vusers: wait the current iteration to end before ..."

but I found LR acted not as expected. I have the log:

 

fiPerformReceive: Fri Jul 19 13:50:23.250: Waiting for readable socket 600 secs, 0 usecs [MsgId: MMSG0]
Abort was called from an action. [MsgId: MMSG-10447]
Ending Vuser... [MsgId: MMSG-15966]
Starting action vuser_end. [MsgId: MMSG-15919]

 

Why? the Vuser was still in Action waiting for the respone from the socket. But LR instruct it directly go to vuser_end...

 

 

P.S. This thread has been moved from Performance Center Support and News Forum  to LoadRunner Support Forum. - Hp Forum Moderator


Viewing all articles
Browse latest Browse all 3978

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>