-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 George,
On 2/22/2010 2:37 PM, George Baxter wrote: > Thanks for everyone's help... it was indeed app code.. some old ugly > legacy code was putting a reference to a request in a thread local > variable and then not cleaning up the thread local reference when the > request ended. When the thread was reused, it was referencing a > request that was no longer valid (been recycled) and all things went > downhill from there. Another coconut! > We're still a bit confused as to why this code works fine in Tomcat > 5.5 and fails so gloriously in 6, but I suppose the recycling model > and maybe the thread handling model is different. Perhaps your app's code depends on this ThreadLocal being leaked across requests or something. I believe that Tomcat 6 (but not Tomcat 5.5) clears ThreadLocals placed in there by webapp code as a protection against memory leaks and weird issues like this. It's possible that your webapp can't exist in such a tidy environment :) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuEJVcACgkQ9CaO5/Lv0PCagACeM6oGNlUcK8/wERIx4goIyDHO QmQAoK3A//rJqMLoKxdMdMS5OeP7fLjD =XEyN -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
