Change session timeout do not work from 20 mins

[ArtemKildyushev]

Hello everyone!

QlikView: Version 2019 SR2

General timeout set in 60 min, any timeouts to application are not installed.

In web-client users  get message that connection lost, after 20 minutes.

After changes in QMC and recommended customization for IE and Chrome it's still do not working.

So, in system logs are written the next reason: "closing the session at the iniative of the client".

And session breakdown is still 20 mins in fact.

Do you know any ideas, hot to fix this?

Thank you!

[Maria_Halley]

@ArtemKildyushev

It sounds like you are using IIS, if so, there are settings that will affect this.

Have you looked at the article below?

This IIS setting is 20 minutes by default and can creates this issue

Application Pool Idle Timeout

Timeout Values Related To QlikView Deployment

[ArtemKildyushev]

@Maria_Halley 

Thank you,

but we are using QVWEBSERVER.

Do you have any ideas about that?

[Chip_Matejowsky]

I agree with Maria in that a 20 minute timeout is typically associated with IIS.  Please confirm by checking QMC > System > About, and if you have QlikView Web Server or QlikView Web Server Settings Service; or on the Windows side, check the Services applet to see if QlikView Webserver or QlikView Settings Service is listed.  If you see Settings Service, then IIS is in use.

[Daniele_Purrone]

Hi @ArtemKildyushev ,

As my colleagues said, 20 minutes is usually the IIS timeout: if you are using QlikView WebServer then there might be some third party tool in the middle terminating idle connections. So, any chance that you might have a firewall or web proxy that does that? Does the issue happen when connecting on localhost on the webserver?

[Maria_Halley]

@ArtemKildyushev 

I was just curious if the suggestions above helped you find a solution?

[ArtemKildyushev · Accepted solution]

@Maria_Halley 

We checked the server settings again and found a few options that we didn't change (cokie and web-configuration). Everything is working correctly now/

Thank you!

[Maria_Halley]

@ArtemKildyushev

I'm glad to hear that it is working for you now!

Would you mind marking one (or more) on the suggestions as "solution accepted"