On 29.07.2010 15:02, Mark Thomas wrote:
The current Manager implementations have slightly different definitions
of 'active session' that I would like to make consistent in 7.0.x (and
maybe backport to 6.0.x)
Ignoring expired and invalidated sessions:
- in the StandardManager, all sessions are primary and all are active
- in the DeltaManager, both primary and backup sessions are active
- in the BackupManager, only primary sessions are active. Backup and
proxy sessions are not active
These leads to some inconsistencies such as
https://issues.apache.org/bugzilla/show_bug.cgi?id=49407
As I see it, there are three options to make this consistent:
1. Change DeltaManager so only primary sessions are treated as active
(i.e. no longer treat backup sessions as active)
2. Change BackupManager so that backup sessions are treated as active.
3. Change BackupManager so that backup and proxy sessions are treated as
active.
Other factors are:
- maxActiveSessions uses the active session count to determine if the
limit has been reached
- the manager app allows data active sessions to be viewed, invalidated
or attributes removed
I intend to make the following changes unless there are any objections:
- modify BackupManager to treat backup sessions as active
- list all known sessions in the manager application
- mark sessions as primary, backup or proxy in the manager application
user interface
- only provide session details in the manager application for primary or
backup sessions (i.e. ones where there is already a local copy of the
full session)
Sounds perfect!
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
