Bill Barker wrote:
The TomcatResolver instance is holding a reference to the Request instance,
and is in a TL. As a result (because of the way the ThreadPool works) it
will live very much longer than just during the processing of a given
Request. This is all fine for all of the current Connectors except Nio/AJP,
since they happen to bind the Request instance to the Thread instance so you
always get the right Request instance.
Adding a setRequest method to TomcatResolver would "fix" this with the
minimal amount of work.
Since TomcatResolver is a very simple object, I replaced the thread
local by a new TomcatResolver.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
