Time-out not working as expected

[wadewilson]

I am seeing an issue with the time-out functionality where time-outs are only occuring if a session is left on a static homepage or on a list view. If a session has an open record, the time out does not occur, even if there is no mouse or keyboard activity. Reading into the time-out property, it seems that this should only happen if a glide.heartbeat event is registered. However there are no such events being fired off while the session is just sitting on the open record.

Has anyone encountered this before? If so, what was the fix?

Or is the system working as designed?

[Mwatkins · Accepted solution]

I have a few ideas:

1) There is a known problem in Helsinki, PRB671499 Session timeout broken by active AMB requests. However, this PRB was fixed in Helsinki Patch 6 and all later versions so it will not affect you. If you wanted to double check you could do this test:

Set glide.ui16.live_forms.enabled = false

See if the issue goes away. If so, then maybe PRB671499 or a similar issue still affects you.

2) Another thing that could be a problem is if you have customized any of your Installation Exits to set the inactivity interval. Do you have any like this?

request.getSession().setMaxInactiveInterval(3600);

3) One more idea: try setting "collaboration.frameset" = false

Did any of these fix it?

Also, I wanted to let you know that, after doing some research, I believe in Geneva and Helsinki the module counts plugin does not extend the life of a session.

[wadewilson]

Hi Matthew,

Seems like we are being affected by PRB671499. Setting ui16.live_forms.enabled to false resolved the issue. I double checked the exits and I don't have anything like that and the collaboration property isn't part of my instance. Or did you mean for me to try adding it?

Manuel

[Mwatkins]

Don't worry about the collaboration.frameset property. After further research it looks like that will only help in the case of instances running Fuji. You can ignore that.