Forcing Seaside to timeout sessions?

Hi all.. I was wondering if there's a way to force Seaside to purge all
existing sessions that might be open.. I had adjusted my session timeout
value to 8 hours to allow me to run w/o timing out my sessions, but I
have a database connection for each Seaside session and have a LOT of
stagnant Seaside sessions lying about and would like to do some house
cleaning.. I tried forcing GC, but that didn't work..

Any ideas?

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Rick Flower wrote:
> Hi all.. I was wondering if there's a way to force Seaside to purge
> all existing sessions that might be open.. I had adjusted my session
> timeout value to 8 hours to allow me to run w/o timing out my
> sessions, but I have a database connection for each Seaside session
> and have a LOT of stagnant Seaside sessions lying about and would like
> to do some house cleaning.. I tried forcing GC, but that didn't work..
>
Nevermind.. I tried the "flush cache" and while that didn't appear to do
anything immediately, the next time I loaded up my Seaside app's page,
the purge seemed to take place and all of my old Seaside sessions
disappeared..

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Am Mittwoch 07 Februar 2007 19:22:58 schrieb Rick Flower: However, it would be nice, if such a purge would happen more often and you
don't have to click on "clear caches" to make it work... Or is seaside's
behaviour with session cleanup an other in the deployment mode? I would
think, that after 10 minutes, if the session time out, it soon would be clean
out of the caches automatically....

Regards,
Martin
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Martin Beck wrote:
> However, it would be nice, if such a purge would happen more often and you
> don't have to click on "clear caches" to make it work... Or is seaside's
> behaviour with session cleanup an other in the deployment mode? I would
> think, that after 10 minutes, if the session time out, it soon would be clean
> out of the caches automatically....
>  
In my case, I had modified the timeout value to 8 hours (a long time ago
for my own reasons) and was doing a lot of new sessions while testing
some css layouts w/i the last few days and this was causing lots of
saved sessions to stick around..  The default is 600 seconds --
configurable via the config page for your app..


_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

2007/2/7, Rick Flower <[hidden email]>:
> Hi all.. I was wondering if there's a way to force Seaside to purge all
> existing sessions that might be open.. I had adjusted my session timeout
> value to 8 hours to allow me to run w/o timing out my sessions, but I
> have a database connection for each Seaside session and have a LOT of
> stagnant Seaside sessions lying about and would like to do some house
> cleaning.. I tried forcing GC, but that didn't work..

WARegistry clearAllHandlers

> Any ideas?
>
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside