0003122: cluster sessions not expiring

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0003122

[Resin]

minor

always

12-05-08 09:15

03-26-09 18:08

Reporter

ferg

View Status

public

Assigned To

ferg

Priority

urgent

Resolution

fixed

Status

closed

Product Version

3.2.1

Summary

0003122: cluster sessions not expiring

Description

(rep by Richard Grantham)

Well, usually it's 60 minutes. The 60 second timeout is set when someone
closes the browser without logging out (JavaScript catches the event and
calls a JSP which sets the new session timeout with
session.setMaxInactiveInterval(60)). This is so that if someone loses
their connection to the internet they will be able to continue working
without issue when it comes back (assuming it's back in under an hour).
The timeout is being set by the JSP but is not acted upon.

Perhaps I should explain the use case. Our application maintains a list
who is logged into the system. It also allows people to lock things for
editing. So that people can't lock things and go off on holiday
preventing others from working we unlock anything they have locked and
clear them out of the logged in list when a session is invalidated.
Right now people are just closing the browser and going home and their
colleagues are unable to continue the work the next day. I'd agree that
half the issue is education ("please press logout") but it's also
something we need to be pro-active about.

Additional Information

Attached Files

Relationships

Notes
(0003937) ferg 03-26-09 18:08	server/015p, server/01nk

Issue History
Date Modified	Username	Field	Change
12-05-08 09:15	ferg	New Issue
03-26-09 18:08	ferg	Note Added: 0003937
03-26-09 18:08	ferg	Assigned To	=> ferg
03-26-09 18:08	ferg	Status	new => closed
03-26-09 18:08	ferg	Resolution	open => fixed
03-26-09 18:08	ferg	Fixed in Version	=> 4.0.0

Mantis 1.0.0rc3[^]

28 total queries executed.
25 unique queries executed.