Skip to main content


QlikWorld 2023, a live, in-person thrill ride. Save $300 before February 6: REGISTER NOW!
Showing results for 
Search instead for 
Did you mean: 
Partner - Creator III
Partner - Creator III

Load testing - prohibit session recovery

In several places in the load testing documentation it says this:

In QlikView 10 there is functionality for remembering thestate for a certain user which is not session based. When simulating manyVirtual Users (VUs), this will imply that all sessions will interfere with eachother. Therefore the setting “ProhibitSession Recovery” must be checked at the Documents tab from the QlikViewEnterprise Management Console.

I don't understand "this will imply that all sessions will interfere with each other".  In some cases we would like to do load testing with session recovery enabled, because that is how a customer has it configured in production.  Why is it recommended to prohibit session recovery?  What is the effect of this setting being checked or not for load testing?


1 Reply

It all has to do with windows authentication.

Typically, load is generated from one client machine which means that each virtual user will authenticate themselves as the user running the load test (if windows authentication is used). If session recovery is enabled, all simulated users will recover and use the same session. This will in effect mean that they invalidates each others state when new actions and selections are performed in the document.

As the load test aims to simulate unique sessions, by checking ProhibitSessionRecovery all virtual users will have their own session and state even though the load is generated from one source machine.

If the virtual users are authenticated in a different way, e.g. header authentication, it does not matter whether ProhibitSessionRecovery is checked or not as long as each userid is used only once during the load test.

Best regards,

Scalability Center