https://issues.apache.org/bugzilla/show_bug.cgi?id=42996
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
--- Comment #13 from Mark Thomas <ma...@apache.org> 2009-05-25 13:02:34 PST ---
Having reviewed the comments, I am reminded of similar issues that have been
reported in the past. Namely, sporadic loss of parameters which is very hard to
replicate.
The reference (in comment #4) to parametersParsed being true before the request
has been processed also rang some bells.
I believe that the root cause is that the application (or possibly the
framework being used - in this case wicket) is retaining a reference to the
request object and attempting to re-use this retained request object during the
processing of a subsequent request. Tomcat recycles request objects so if an
application retains a reference to a request then the processing of subsequent
requests can break. This hypothesis is also consistent with comments #7 & #10
Of course, this is all supposition based on experience. Although I am closing
this as INVALID, if anyone does find a reproducible test case that points to a
Tomcat bug then please do re-open this issue, attach your test case and someone
will take a look.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
