tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 6360] - request.getSession(true) may return null
Date Thu, 14 Feb 2002 19:37:11 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6360>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6360

request.getSession(true) may return null

william.barker@wilshire.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From william.barker@wilshire.com  2002-02-14 19:37 -------
AFAIK the only way that request.getSession(true) can return null is if the 
number of active sessions exceeds maxActiveSessions.  Also, rd.forward is 
executed in the same thread as the original request.  

This looks very much like a common programmer error when using frames.  The 
browser will usually request the frames in parallel, so that each one ends up 
getting its own session.  The fix is to do:
<frame src="<%= response.encodeURL("/frame1.jsp") %>" ...

Since I can't reproduce this, I'm marking it as invalid.  Feel free to re-open 
with a test case that reproduces this.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message