DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=31523>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31523 Request parameters are not always passed to HttpServlet.service ------- Additional Comments From [EMAIL PROTECTED] 2004-10-04 11:04 ------- What you mention would hint at a race condition, but the threading (or lack of) of the parameter parsing code is really obvious. Note that none of the objects provided are even remotely thread safe, which is in line with the servlet sepcification. The parsing of the request parameters is lazy, which might be the big difference between Tomcat and other servers. You could for example test that by adding a valve in the Tomcat pipeline which would trigger the parsing of the request parameters much earlier (an empty valve with request.getParameter("foo") in it would do). You could try a filter, but it's already inside the user code, so depending on what the framework does, it could be too late already. Again, you provide assertions that Tomcat is necessarily at fault. IMO, it's rather one of the other components being used which are at fault (one big hint is look at if they're using threads). If the workaround mentioned above fixes the issue, then it is not a Tomcat issue. The only way to prove the problem is with Tomcat would be allow me to reproduce the issue. So I would need a simple WAR (= not using Cocoon) with a form exhibiting the problem. Otherwise, there's really no way I would be able to reproduce the issue (which, according to you, is hard). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
