Aaron Held wrote:
Yes, currently with SessionDynamicStore, and SessionMemoryStore, the sessions are persistent acrsoss AppServer restarts. This causes problems for anyone keeping data in a session object which can't be pickled.If someone wants to propose a NonPersistentMemory store as an experimental feature, I could see including it. But I want to release 0.8b2 on Wednesday, and I would like ot to be a final beta prior to release.
What is meant by NonPersistentMemory? Are we talking about when the app server shutsdown and restarts? I had a problem where when I restarted the app server I did not want the old sessions, so I added like to clean the seesion folder.
You could always force it clear by calling application().sessions().clear() However this can't be done in a shutDownHandler because those get called after the sessions have been saved.
I'm sure some solution to the issue will be forthcoming after the 0.8 release.
I think that the next session code / API upgrade should pay more attention to the load balacing and app server affinity. - Maybe a session prefix code could tell the adapter what server the session started on - so the adapter could keep that user on that app server for the duration of thier visit. I used another cookie for this, but it was a hack and I abandoned it in favor of a bigger server.I haven't looked into any load balancing issues myself, just curious, how are you doing this, and with which adapter? Are you running multiple AppServers on a single system? Or directing them off to different systems in the adapter? Or using Apache for this?
-Aaron
-Stuart-
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel
