tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jess Holle <>
Subject Re: Custom HttpSession passivation?
Date Fri, 03 Dec 2004 16:41:43 GMT
Remy Maucherat wrote:

> Jess Holle wrote:
>> Remy Maucherat wrote:
>>> It's called persistent manager, and it's the same place as the 
>>> standard manager, in the session package.
>>> There's even docs: 
>> Thanks for the pointer!
>> It appears to have what I need/want except for one feature, though 
>> I'd like to confirm this.
>> Is maxActiveSessions the maximum number of sessions at one time?  Or 
>> is it rather the maximum number which have not been passivated 
>> allowed at one time?
> If maxActiveSessions is reached, it will (at the moment) refuse the 
> creation of a new one (like for the StandardManager).

To be really clear does "is reached" mean there are 'maxActiveSessions' 
*active* (non-passivated) sessions?  Or does it mean there are 
'maxActiveSessions' sessions which have not been invalidated and/or 

[We need the former -- badly enough to add it ourselves if necessary.]

Jess Holle

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message