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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical ------- Additional Comments From [EMAIL PROTECTED] 2002-02-12 12:05 ------- For our environment I've found a fix to resolve the problem: + use a dispatcher-servlet (servlets are do not have the encountered problem) + synchronize the processed request to the session-object (required to ensure that only one resource-request is performed simultaneously) + include the specified resource (a forward to the resource would create a new thread and the request would be de-synchronized again) This solution is quite slower than the original implementation, but does never fail - independent how many frames are used. Further tests indicated that the HttpServletRequest seems to be re-initialized after a parallel request within the session has been finished. The re- initialisation is indicated by loss of the associated session. This applies at least to Tomcat versions 3.1 and 3.3! -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
