Qlik Community

Qlik Scalability

A group dedicated to advancing Qlik scalability and performance. In this group we will share knowledge on how to perform load tests of Qlik products.

Not applicable

Re: QV Scalability Tools (QV10,QV11,QV12)

Hi Sebastin,

Thanks for your quick response.

As pointed out by Pawel due to wrong machine name in the TestLogMeta.txt the CPU and RAM charts were not being generated. But after correcting it my charts are being generated correctly now.

I am running the test for a single user and run the script in the jmeter , there is no error in  it.

As pointed above I am using header authentication with the help of FIDDLER tool.

Now my only concern is that in the event  and session logs I am getting a error stating that :

Named CAL session for user "CUSTOM\QVJEFF" stopped

Session stop reason : Killed because Named User Cal was needed from another client

image003.jpg

I am having 33 named cals with me.

The file in the header authentication by default contains the following names and password:

usr.PNG

As soon as I connect the tool with the server these all usernames are accumulated in the server in form of named cals. Please find the attached image :

usr2.png

But as suggested above to use header authentication and DMS authorization. I am following all the scenarios , but still getting the same type of error. Am I missing something here. Please suggest.

One more thing is there any tutorial video of this as there is one in the qliksense scalability tool. As I was able to run the qliksense scalability tool easily with the help of  tutorial video.

Employee
Employee

Re: QV Scalability Tools (QV10,QV11,QV12)

Hi,

If you get the same error then I suspect the tool is not running with header. You mention using fiddler but that will inject a header in your browser session, not the scalability tool.

So for the tool, if you check on the properties tab, have you checked header as authentication and then given the proper headername (QVUSER) and a reference to a file containing usernames? I can see that you have up to user28 in the QMC and the screenshot of your file tells us it should only go to USER10 so that does not seem configured correctly.

As a sidenote, we recommend using your own file for the generated usernames instead of the one included for the reason stated above - it is just an example and includes only 10 users. Also, password is not required for header users.

Not applicable

Re: QV Scalability Tools (QV10,QV11,QV12)

Hi,

You must be talking about this checkbox.

28.png

I suppose that since I am giving the usernames to the tool through txt file and they are showing in the server as shown in the above post, it implies that it must be connected to the server.

Do I have to specify all the cals name in the txt file.since there are some cals which I have already allocated to some other user.

Also in the general tab in the licenses section I have selected the checkbox Allow dynamic CAL assignment does this checkbox need to be selected?

Secondly the logs are

20170612T132358.000+0500 20170620T110409.000+0500 4 700 Information QVGeneral: Document Load - ODE1: Document D:/Qlikview_Revamp/Final/Application/Primary_Sales_Application.qvw, AuthenLev(1). Authuser()

20170612T132358.000+0500 20170620T110409.000+0500 4 700 Information QVGeneral: Server - UpdateSharedFile: updating DONE for document D:\QLIKVIEW_REVAMP\FINAL\APPLICATION\PRIMARY_SALES_APPLICATION.QVW

20170612T132358.000+0500 20170620T110410.000+0500 4 100 Notice CAL usage: Named CAL session for user "CUSTOM\TESTCLRC1" stopped

20170612T132358.000+0500 20170620T110410.000+0500 4 700 Information CAL usage: Named CAL "CUSTOM\TESTCLRC1" was in use on another client - killed.

20170612T132358.000+0500 20170620T110410.000+0500 4 700 Information Session stop reason: Killed because Named User Cal was needed from another client

20170612T132358.000+0500 20170620T110410.000+0500 4 700 Information CAL usage: Named CAL "CUSTOM\TESTCLRC1" now used - ok.

20170612T132358.000+0500 20170620T110410.000+0500 4 100 Notice CAL usage: Using CAL of type "Named User" for user "CUSTOM\TESTCLRC1". Named user cals in use: 1

20170612T132358.000+0500 20170620T110429.000+0500 4 100 Notice CAL usage: Named CAL session for user "CUSTOM\TESTCLRC1" stopped

20170612T132358.000+0500 20170620T110429.000+0500 4 700 Information Session stop reason: Killed because Named User Cal was needed from another client

What does AuthenLev(1). Authuser() imply?

Not applicable

Re: QV Scalability Tools (QV10,QV11,QV12)

Hi All

Has anyone had a problem with 'Select Bookmark' option in QV Scalability regression script? No error is generated but it just seems to ignore the task completely.

Regards Nicola vd Merwe

Using:

QlikView: 11.2 SR12

QV Scalability Tool: 1.2.1

JMeter: 3.0 as well as 3.1

Scenario:

Scenario.png

Output:ScreenShotOfXML.png

Employee
Employee

Re: QV Scalability Tools (QV10,QV11,QV12)

Hi,

Yes that is the one I meant to check.

You need unique names in the textfile you provide to be used as usernames, for every user you want to simulate you need a unique row in the file. Otherwise you will end up using the same use over and over again which will result in it killing it's own session.

As for the logs, I am not sure about those. There is a slight slight chance that the help documentation has information about that.

Employee
Employee

Re: QV Scalability Tools (QV10,QV11,QV12)

Hi Nicky,

The apply bookmark action is currently not supported for regression script. Which means that the result you get is expected one. For all not supported actions there will be no traces in the result XML files. List of supported actions can be found in Regression Testing document (page 2) in Documentation folder.

The workaround for this would be to create the script which in which selections which are part of the bookmark are done one by one.

We might look into adding bookmark support for regression in the future.

Kind regards.

Partner
Partner

Re: QV Scalability Tools (QV10,QV11,QV12)

Hello,

Does the scalability tool for qliksense support Core based unlimited tokens for testing?