>Does the PersistentManager help not to persist sessions across 
>container start or restart ?

the default standard manager does this

Filip
----- Original Message ----- 
From: "Mufaddal Khumri" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, September 17, 2003 12:22 AM
Subject: Re: cleaning up sessions ...


Hi,

Does the PersistentManager help not to persist sessions across 
container start or restart ? or does it do across webapplication reload 
/ restart ? (by container i mean Tomcat and by webapplication i mean a 
webapp that you run within Tomcat) From the documentation it seems that 
it helps not to persist the session across container restart or reload. 
If thats the case reloading my webapp only will not force the active 
sessions to that webapp to get destroyed or invalid.

Am i understanding this correctly ?

What I am trying to do:

I have a webapp called MyApp that runs in Tomcat. When i restart or 
reload this webapp - MyApp (not restart Tomcat ) ... i want to 
invalidate all sessions to this webapp - MyApp. It could very well 
happen that when i reload MyApp , there could be users using that 
application and have sessions to it. In my ServletContextListener for 
MyApp i do cleanup work and initialization work. At this point i want 
to invalidate all active user sessions too - i want to do this inorder 
to detect that and redirect them to the login page where they would get 
a new session and then i would allow them to go to where they were 
originally trying to go.

How do i achieve this ?

Thanks.

On Wednesday, September 17, 2003, at 12:34  PM, Mufaddal Khumri wrote:

> When i specify saveOnRestart:"false" and reload or start my webapp, 
> the users navigating the website now have an invalid session .. on top 
> of all pages i do a checkAuthetication .. how do i check if the 
> session is active or not ? .. so that i can detect that and redirect 
> them to the login page , before letting them go to where they were 
> trying to go.
>
> <Manager className="org.apache.catalina.session.PersistentManager"
>               debug="0"
>               saveOnRestart="false"
>               maxActiveSessions="-1"
>               minIdleSwap="-1"
>               maxIdleSwap="-1"
>               maxIdleBackup="-1">
>                 <Store 
> className="org.apache.catalina.session.FileStore"/>
>  </Manager>
>
> On Thursday, September 18, 2003, at 12:30  AM, Shapira, Yoav wrote:
>
>>
>> Howdy,
>> You can simply tell tomcat not to persist your sessions.  You don't 
>> have
>> to write any code.  Read the PersistentManager documentation and
>> comments in server.xml.
>>
>> Yoav Shapira
>> Millennium ChemInformatics
>>
>>
>>> -----Original Message-----
>>> From: Mufaddal Khumri [mailto:[EMAIL PROTECTED]
>>> Sent: Wednesday, September 17, 2003 2:31 AM
>>> To: Tomcat Users List
>>> Subject: cleaning up sessions ...
>>>
>>> I have got a ServletContextListener that does initialization and
>>> cleanup for my webapp. I was wondering if there was a way to 
>>> invalidate
>>> all sessions to my webapp in this Listener ? If not, in what way can 
>>> I
>>> invalidate all sessions when i start / reload my webapp ?
>>>
>>> Thanks
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>> This e-mail, including any attachments, is a confidential business 
>> communication, and may contain information that is confidential, 
>> proprietary and/or privileged.  This e-mail is intended only for the 
>> individual(s) to whom it is addressed, and may not be saved, copied, 
>> printed, disclosed or used by anyone else.  If you are not the(an) 
>> intended recipient, please immediately delete this e-mail from your 
>> computer system and notify the sender.  Thank you.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to