Chuck, Valid points.
I was hoping that doing it this way would also provide me with replication of this data between several tomcat instances. Odviously I would need to setup session replication between them. Also it would allow for session data persistence should tomcat be restarted etc. I could grab the requestedSessionId from the request and then use that to look up the session data. I know that tomcat provides some way of persisting session but the documentation doesn't seem to be very good. Ben On 12/19/06, Caldarale, Charles R <[EMAIL PROTECTED]> wrote:
> From: ben short [mailto:[EMAIL PROTECTED] > Subject: Notification of expiring sessions > > I want to store user session data into a database rather than in the > session, to conserve memory. Unless your session data is huge, you're probably consuming more memory by accessing the data base rather than keeping it simple. There are a lot of objects that have to be created and maintained for every DB connection, statement, result set, etc. Also, your original session data object(s) will remain in the heap until garbage collection runs, so are you really conserving memory? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
