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 20:02:32 GMT
Jess Holle wrote:

> 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 destroyed?

Sorry for the dumb question.  The docs are ambiguous but the code is not.

[The meaning is the former -- and I so happy, assuming this works.]

Jess Holle

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

View raw message