Itll timeout the user session with the server. That timeout is configured in the Domino Directory.

I would strongly recommend adding keepalive to any pages where this matters, refreshing 2 min prior to the smallest session timeout. it is often a better resource handler, cleaning up closed web pages more effectively & quickly.

I dont have a Domino Directory readily available, so, going from memory ...

I think the setting is in the "Servers" document under "Internet Protocols". From there its looking for the Web server's "idle session timeout". Beware, there are multiple timeouts, youre not looking for the servlet timeout, and youre not looking for the Notes session timeout. It is associated with either HTTP or the Web Server.

The timeout should be about the same as the application's session timeout.

If you have separate websites on the server, there may be something in the website doc too. I dont remember for sure, but it is also in the Domino Directory.

Which says the server never drops a thread, so I would think that the XPages time out settings would be the time out. But that does not appear to be the case. XPages Session and application timeout are both 480 minutes, but sessions seem to be timing out at about 30 minutes. I can set teh keepalive and it says to set it for a few minutes less than the default but which default?

I would think a zero setting will push the server to default:30 minutes. Set it higher, it'll sit idle, taking up memory for longer for people who have left.

A keepalive at 27 min would keep the server session and the app session alive as long as someone  has a page open. Memory frees faster on those with no pages open, while the session remains on those who still have the page open.

I set up an extensive data input form this way with a lot of comment fields, and it worked well for that.