On 14/09/05, James Shaw <[EMAIL PROTECTED]> wrote: > I have two issues relating to sessions: > > 1) Sessions seem to be expired too soon. This happens very > infrequently for me (perhaps 1 in 1000 requests). I'm adding some > HttpSessionListeners and HttpSessionAttributeListeners to attempt to > locate this problem, but have little to go on at the moment. > I have some more info on this problem. During the login process, the original JSESSIONID that tomcat gives to the browser is being lost and a new HttpSession with a new id is being created. So either the browser is not sending the cookie containing the session id, or Tomcat is somehow losing the id.
Does anyone have an idea what this problem could be? Perhaps you could point me to some information about how Tomcat receives cookies and maps these to their respective HttpSession objects. Thanks James Shaw --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
