We're deployed with all of our timeout settings set to 30mins, but users are still getting dropped after 5 mins:
|20161125T151313.000Z||20161128T104431.000Z||4||700||Information||Session stop reason: Socket closed by client|
|20161125T151313.000Z||20161128T104431.000Z||4||100||Notice||CAL usage: Named CAL session for user "DOMAIN\ADAM.DAVIES" stopped|
We do access via an F5 which we think is the issue but just want to confirm that the above message is Qlik thinking the user has disconnected and not Qlik disconnecting the user?
Solved! Go to Solution.
And the answer for anyone who comes here in the future was
There's a global tcp profile for all tcp sessions outbound that has an idle timeout of 360 secs
Probably user disconnect. You can check yourself, for that user at that time, in the sessions log created in the same catalogue as the eventlog.
Ok bit more info
The user above is me, I just left the browser window open for 5 mins and it (consistently) times out
This is on our server which sits in the DMZ running QVWS
If I connect directly to the server using our internal FQDN then I don't get timeouts, that server is running IIS
Our technical chap says he can see the TCP closing but it is coming from the client not the F5 so it must be something else
there could be, but thats beyond my technical knowledge!
I just checked all browsers again and I didn't get kicked with IE.... retesting now as I might have been too quick off the mark