1) Does your browser have cookies enabled? If not, you need to rewrite all
your URLs, using HttpServletResponse.encode[Redirect]URL().
2) Are you defining a cookie or URL parameter names "jsessionid"? That one
is used by Tomcat to keep track of the session, and shouldn't be set by the
servlet.
3) Does HttpSession.getId() keep returning new IDs, and HttpSession.isNew()
keep returning "true" on each call to your servlet?
As for documentation, the servlet spec goes into this stuff. You can
download it at,
http://java.sun.com/products/servlet/download.html
-- Bill K.
> -----Original Message-----
> From: Roberts Huw [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 02, 2001 3:21 AM
> To: '[EMAIL PROTECTED]'
> Subject: Problem with session tracking. Please help
>
>
> Hi All,
>
> We're having a problem with session tracking.
> We are using tomcat pretty much "out of the box", without integrating
> with apache or anything like that.
> We are attaching an attribute to the session which we want (reasonably
> enough) to be "per session".
> We are then sending requests for information to tomcat from several
> different client machines (sometimes logged on as the same
> user, sometimes
> as different users, sometimes using Netscape, sometimes using
> IE). All
> machines are running Windows NT4.0.
>
> What we are finding is that the Session objects are being
> indiscriminately
> associated with the servlets. We are getting the right number of
> session attributes created, but when we refresh the page we find that
> the new request is associated with the wrong session.
>
> Help? Is there anything obvious we are missing? Is there a
> document on
> how the session management works in tomcat?
>
> We are using tomcat-3_3-m1
>
> Thanks a lot,
> Huw
>
> **************************************************************
> **********
> The information in this email is confidential and is intended solely
> for the addressee(s).
> Access to this email by anyone else is unauthorised. If you are not
> an intended recipient, you must not read, use or disseminate the
> information contained in the email.
> Any views expressed in this message are those of the individual
> sender, except where the sender specifically states them to be
> the views of Capco.
>
> http://www.capco.com
> **************************************************************
> *********
>
