Jess Holle wrote:
FYI, it would appear that this is a case of someone passing a
ServletRequest object to another thread and invoking methods on it at
just the wrong point in time so as to utterly corrupt a later request.
Changing the code to make an appropriate copy of the ServletRequest
object and pass that instead has resolved our issue.
At a more general level, I certainly understand that the ServletRequest
interface makes no guarantees about thread safety -- and performance
reasons for not making the implementation thread-safe. That said, it's
certainly quite surprising to see this impact later requests due to
recyling behavior!
In any case, thanks for reporting the resolution of the issue, and the way in which it was
resolved.
Some people never do that and it is annoying, because it leaves an inconclusive trace in
the archives, possibly causing someone else in the future to be misled and waste time
chasing dead-ends.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
