If its in web.xml twice - it would be called twice.
sessionDestroyed is called when the container kills the session. Which is done during session timeout or session.invalidate()
-Tim
Allistair Crossley wrote:
Thanks Tim. Done that ... any reason why sessionCreated is always called twice?
2004-08-19 12:31:02,920 - DEBUG (com.qas.newmedia.intranet.iq.IQSessionListener:31) - new session: 0E3C9F21B145FF21903D8D35E540217F 2004-08-19 12:31:02,920 - DEBUG (com.qas.newmedia.intranet.iq.IQSessionListener:31) - new session: 0E3C9F21B145FF21903D8D35E540217F
Also, sessionDestroyed I am guessing is not actually called when a user closes their browser but on session timeout after inactivity correct?
Allistair Crossley
-----Original Message----- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: 19 August 2004 11:48 To: Tomcat Users List Subject: Re: [OFFTOPIC] Removing attribute from all HttpSessions
Look at the SessionListeners to register all the sessions that match your criteria into a map. Then whatever is listening on your invalidation strategy can update the map. (Actually - the sessions in the map)
-Tim
Allistair Crossley wrote:
Hey,
I am putting a page caching stategy into place per user
session. However, there are times when I need to refresh all the caches for all users. For example, let's say 5 users have a cached version of page 5. An external event causes page 5 to invalidate. I need an effective strategy to flush all sessions with page 5 cached.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
