tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kief Morris <>
Subject RE: req.getSession(true) problems with 3.2.1
Date Mon, 12 Feb 2001 20:01:45 GMT
Richard Downey typed the following on 12:37 PM 2/12/2001 +0000
>I can now re-create the stack overflow problem with the two attached
>servlets. The problem only occurs when you put something into the session
>(in my case I'm using the deprecated getValue,  putValue for compatibility
>with Websphere etc but I *have* tried it with getAttribute / setAttribute
>and it still falls over).

I've finally pinned this one down: it's bug 504, reported at:

Basically, the session is getting wiped out when it is forwarded under exactly 
the wrong circumstances. The stack overflow is because you are recursively 
forwarding: sessiontest2 forwards to sessiontest which then forwards to 
sessiontest2 again. If all goes well this is fine, but because of a bug in Tomcat
the recursion never terminates.

I've fixed this, it should go into the upcoming 3.2.2release. Stay tuned.

Out of curiosity, are the recursive forwards really necessary? Can't
you just put the code from sessiontest into a normal class file? It
would be safer and cleaner.


View raw message