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
We now have QVWS running on our main server and the stand alone web front end in the DMZ
The internal server does not time out
The external one (via F5) does
We pointed the F5 to the internal server, and this does not time out
So it is something to do with the server in the DMZ but I have no idea what to look at.
The only thing I can think is we are using a specific domain name to connect and something isn't working as it hops between the two ip addresses
If the internal works but the external does not the question is -and sorry for the obvious: what are the differences between both? Things I would recheck:
- software (QVWS config vs IIS recycling or session timeout in the service),
- configuration of the probes in the balancer,
- configuration of QlikView webserver in the QMC,
- internal has a single web server and external has more than one web server,
- DMZ uses a proxy which is applying the timeout
After all, it is not that it does not work, just that it times out earlier than expected and from what I can see, always the same timeout (not erratic like 30 seconds now and 60 seconds one hour later and so).
I can't thank you enough for your time on this, its really got me foxed!
Software- should be exactly the same now the internal is running QVWS
Network- could be it
Balancer- Not sure we have one as we only use the one front end, the one on the server I purely use for testing.
Qlik Server- Should be the same as they both point to the same QVS
DMZ- could be it
I completely agree, it does work and it works well.. its just the user consistently gets kicked after 5 mins of idle time, the issue is that we don't want to deploy this to snr management as they obviously take a lot of phonecalls etc and we don't want them to loose their sessions.
I am sure it has to be something in the connection between the QVWS in the DMZ and the QVS. However because the DMZ has a read only AD then we're not doing anything fancy with ticketing and the service just runs under the same domain account... it just works nicely. I am sure the answer lies within our network team but they're looking for some pointers I think
Not the best method and probably too cumbersome but still useful is to use the Scalability Center tools (basically JMeter) to emulate users longer than 5 minutes and see what the logs record, which exact error does JMeter get when it is timed out and which system is sending that message.
ON a second thought, you could still do it without all the JMeter hassle by using the developer console in the browser, all IE, Firefox and Chrome have good, built-in consoles/developer tools which can help you troubleshooting where the issue is.