You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by DAK <da...@dotech.com> on 2001/06/11 23:42:06 UTC

session invalid?

I'm seeing something strange. (would I write if it wasn't strange?)
I have a servlet that is used to generate an image. I include the URL to 
it as output from another servlet. (so it is embedded in the page 
generated by the first). Somewhat regularly, it fails to get the session 
object. I call request.isSessionValid() and get false. If I reload the 
page, it works fine. I'm not sure where to look. I'm using Tomcat 3.2.2 
on Solaris 8. I've looked that the source for 3.2.2 and can't find 
anything about getting the session object that looks out of whack. The 
only thing that could cause this was if the session was temporarily 
invalid. The valid flag shouldn't be subject to race conditions since it 
is set and not changed until the session is recycled (or invalidated). I 
know I'm not marking it invalid since my other servlets can continue to 
get the session object and that same preview servlet that failed, will 
succeed the next time around.

Any pointers for the more seasoned folks? I'm going to try switching 
from session cookies to see how that works.

   David


Re: session invalid?

Posted by DAK <da...@dotech.com>.
Got it figured out. I turns out that the proxy within Xerox was messing 
up the cookies. Disable the proxy and all is well!

   David

DAK wrote:

> 
> I'm seeing something strange. (would I write if it wasn't strange?)
> I have a servlet that is used to generate an image. I include the URL 
> to it as output from another servlet. (so it is embedded in the page 
> generated by the first). Somewhat regularly, it fails to get the 
> session object. I call request.isSessionValid() and get false. If I 
> reload the page, it works fine. I'm not sure where to look. I'm using 
> Tomcat 3.2.2 on Solaris 8. I've looked that the source for 3.2.2 and 
> can't find anything about getting the session object that looks out of 
> whack. The only thing that could cause this was if the session was 
> temporarily invalid. The valid flag shouldn't be subject to race 
> conditions since it is set and not changed until the session is 
> recycled (or invalidated). I know I'm not marking it invalid since my 
> other servlets can continue to get the session object and that same 
> preview servlet that failed, will succeed the next time around.
> 
> Any pointers for the more seasoned folks? I'm going to try switching 
> from session cookies to see how that works.
> 
>   David
>