i am reviewing a list of the session ids in my SessionCount's HashSet, and have acquired some more information:
when someone logs in, two session ids are getting added to my SessionCount's HashSet, and one of them is a blank session id. i'm not sure if it's null or "". the only session that appears to be destroyed after the timeout is the blank one. -----Original Message----- From: Barclay A. Dunn [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 1:44 PM To: 'Tomcat Users List' Subject: RE: active session counting, redux ok, that is helpful. (both things.) after changing the timeout to 5 min, i confirmed that indeed it was destroying a session after 5 min. the reason i went with HttpSessionListener was i had read that using HttpSessionBindingListener, once the session was unbound, you couldn't get any info on that session. the reason i went with my user implementing HttpSessionListener was i had read that you had to implement it in an object that would be bound to the session, and my user object is the only one i am certain to bind to the session. now, i now you guys have had endless discussions about active session counting (hence my subject line contains "redux"), and i apologize for bringing up an old and re-re-rehashed topic, but i could still use a little more advice. i haven't quite got it working yet, but nevertheless i guess i'm ready now to hear what i should have done instead of what i did do. thanks, Barclay A. Dunn Senior Developer www.HappyPuppy.com 33-41 Newark St, #1A Hoboken, NJ 07030 201-269-6302 -----Original Message----- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 1:13 PM To: Tomcat Users List Subject: RE: active session counting, redux Howdy, >hmmm. thanks for your thoughts, and good question. upon logout, among >other things, i am calling session.invalidate(). should i do something >different? Invalidate is close to but not the same as destroy. Specifically, the container is not required to destroy a session when you invalidate it. For experimentation and to verify your solution, set the session timeout to 5 minutes in web.xml, create one session, then wait 5 minutes for it to be timed out and a bit more for it to be destroyed, and see if your listener handles it properly. Yoav Shapira 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]
