Forum Discussion
pether
15 years agoNew Contributor
eviware support wrote:
I'm not sure how the sticky sessions are implemented, but if they rely on something like a cookie to be presented from the client, then this should be possible by using soapUI and the soapUI Runner instead of the very basic functionality that the built-in Web Page runner provides.
Thanks for the rapid response, but my problem is the opposite. I don't want the session to be kept between calls. I want every call by the webpage runner to be called as a new user without any session state.
So maybe it's a bug in LoadUI, I don't know anything about the implementation of the browser in LoadUI. But it behaves like it stores the sessionid between calls. Should be cleaned away after each call.
Sticky session on apache using loadbalancer checks the sessionId on a request and make sure all request with the same id get passed to the same worker node. So causes problem when doing loadtesting using loadUI since all request only hit one of the worker nodes all the time.
All the best, Pether