Qlik Scalability Tool Testing

[anjali24]

Hi Community,

We are running the scalability tool, and all the necessary configurations are in place. When we keep concurrent users at 1, it works fine. The status is success. But when we are increasing the count (eg: 2), then we are getting the error Failed connecting to sense server: Failed connecting to sense server: Error connecting to Sense: unexpected HTTP response status: 403.

[hugo_andrade · Accepted solution]

Hi @anjali24 ,

I can think of two things that could be impacting.

• Confirm there's a license rule that allows your fabricated users to get a license assigned
• Confirm the security rule allows your users to access the published app on the stream

Most likely, it's an issue with the Security Rule.

[Sivapriya_d]

Hi @anjali24 
Possibly the reasons mentioned by @hugo_andrade .
Whats your authentication type in the virtual proxy used for scalability tool?

[anjali24]

Hi @hugo_andrade ,

Thanks for your reply. I have added the license rule as well the app is pulished in Everyone stream so the users has access to it.

[anjali24]

Hi @Sivapriya_d ,

Thanks for your reply. The authentication type in the virtual proxy is Header authetication dyanmic user directory.

[Sivapriya_d]

Hi,

Are you listing down the user list one by one ?
Instead can you try with below

[anjali24]

Hello, No. I'm not listing th users manually, It is getting created dynamically.

[hugo_andrade]

@anjali24 ,

How many available licenses you have?

Could you please share details on that for us?

Do you see the new users get created when you check in QMC? 

[anjali24]

Hi @hugo_andrade ,

Thanks for your reply. We have 10 licenses, out of which 3 are allocated to different users and in the login access pass access rule I have added 4. And also yesterday when th users got recreated it is visible in Qmc, but I noticed that the licenses to them are not getting allocated automatically, you think this might be the cause? I tried to apply the license manually but still I was facing same the same error. Can you help here.

[Sivapriya_d · Accepted solution]

Hi @anjali24 
Change your "prefix" in user setting like below and test