Forum Discussion

pether's avatar
pether
New Contributor
16 years ago

Webpage runner dealing with sessions

Hi all,

Currently doing some testing using loadUi where I am using apache as loadbalancer in front of a few jboss servers. The apache is setup with stickysessions.

The webpage runner seems to reuse the sessionid it recieves from the server, that causes great problem since in my testcase I will always hit the same backend jboss server.

Just running loadui locally without any agents.

Any ideas on howto solve this or is it just a user error ? Tried with and without propage sessionId settings..

All the best, Pether

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hello,

    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. In soapUI, there is a "Maintain HTTP session" option in the TestCase Options which should provide what you are looking for. Good luck!

    Regards,
    Dain
    eviware.com
  • pether's avatar
    pether
    New Contributor
    16 years ago
    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
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hello,

    Sorry, I wasn't clear. What I meant was that if you make sure the checkbox is NOT checked in soapUI, then the session should not be reused. In loadUI the session is reused, which you have noticed. If you have a suggestion for how you would like to see this behavir improved, please post it in the feature request section of the forum!

    Regards,
    Dain
    eviware.com