Sessions tomcat DesktopCleanup [closed]

answered 2018-03-02 15:33:45 +0800

cor3000
6280 ● 2 ● 7

technically there is no difference between closing a browser(tab), navigating away for reloading the page. Each of these operation is triggered by the same "onBeforeUnloading"-event listener and will send the same "rmDesktop"-command to the server in order to destroy the desktop (including DesktopCleanup). So unfortunately i can't think of a solution from that angle.

At server side you could do something slightly different (maybe not 100% perfect but maybe good enough).

Once the number goes down to 0 (last desktop destroyed) you can - instead of invalidating the session - set a short maxInactive interval (e.g. 10 seconds) so that the session will not invalidate immediately. If the user just refreshed the page the next request will (hopefully) arrive in time, to reuse the previous session. In your DesktopInit listener you can then again count up to 1 and restore the original maxInactiveInterval to extend the session.

If the user really left the page the session will then timeout after 10 seconds and trigger a SessionCleanup Listener where you can perform your logout/cleanup tasks.

Does this make sense/help with your scenario? As said it's not perfect but a reasonably short period should be sufficient to allow page refresh - while timing out reasonably early otherwise.

Robert