Every 30 minutes QvAjaxZfc/GetWebTicket.aspx component takes ~30 seconds to generate webticket token

[nishageorgetril]

QvAjaxZfc/GetWebTicket.aspx caches the user details from windows group and every 30 minutes this component takes ~30 seconds to generate webticket token

We are experiencing a slowdown during execution of /QvAjaxZfc/GetWebTicket.aspx.

Every 30 minutes, the web service has a response time of 20-30 seconds. Usually response time is 200-400ms.

We have tried both NTLM and IP Whitelisting options, but we experience the same slowdown.

We have reviewed IIS configuration and make sure the Recycle option is running outside of business hours. Also we have disabled the IddleTimeout option.

HAS ANYONE ENCOUNTERED SUCH AN ISSUE? This is very strange.

I'm attaching IIS logs where you can see the slowdown.

2020-09-18 00:02:19 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 27077

2020-09-18 00:03:20 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 1

2020-09-18 00:04:23 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 0

2020-09-18 00:05:41 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 1

2020-09-18 00:06:57 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 1

2020-09-18 00:08:12 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 1

2020-09-18 00:09:27 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 0

2020-09-18 00:10:42 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 0

2020-09-18 00:11:57 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 1

2020-09-18 00:13:13 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 1

2020-09-18 00:24:32 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 1

2020-09-18 00:25:49 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 0

2020-09-18 00:27:04 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 1

2020-09-18 00:28:19 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 0

2020-09-18 00:29:34 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 1

2020-09-18 00:31:04 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 1

2020-09-18 00:32:46 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 27073

2020-09-18 09:52:58 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 15184

2020-09-18 10:23:40 10.56.230.90 POST /QvAjaxZfc/GetWebTicket.aspx - 80 - 34.192.31.223 Zabbix 200 0 0 27070

[Brett_Bleess · Accepted solution]

I believe what you are hitting is the following setting in the QVWS Config.xml file located by default in C:\ProgramData\QlikTech\WebServer

<SessionCookieTimeOut>30</SessionCookieTimeOut>

Bumping that timeout should alleviate the issue, or reduce things etc., but you will have to judge how long to make the cookie active etc. and offset any security risks associated with lengthening that period of time.  Hopefully this does the trick.

Regards,
Brett