2010/2/19 Pid <p...@pidster.com>: > On 19/02/2010 16:49, Christopher Schultz wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Pid, >> >> On 2/19/2010 11:39 AM, Pid wrote: >>> >>> !ThreadSafe >>> >>> This type of error was a symptom of the request/response being held as >>> an instance field in at least the last one of the couple of recent times >>> we saw this AFAICR. >> >> I certainly agree that these classes aren't threadsafe, but I don't see >> where anything gets nulled-out, so even if it's a >> threading/synchronization issue because these guys are holding-onto >> references to response objects and stuff, I can't understand the NPE >> happening. Weird behavior? Yes. NPE? I'm not sure. > > If I could find the *&%$ thing in the archives... >
1. The OP (chinmaytotekar) never mentioned what Tomcat version (s)he was using. What a disgrace. 2. For example of similar stack traces: (searching for "Tomcat NullPointerException MimeHeaders" will give more hits) http://old.nabble.com/NullPointerException-in-MimeHeaders-tp27419583p27419583.html http://old.nabble.com/NullPointerException---org.apache.tomcat.util.http.MimeHeaders.clear%28MimeHeaders.java%3A130%29-tp24950113p24950113.html https://issues.apache.org/bugzilla/show_bug.cgi?id=47655 (Not so much.. I thought there will be more of those) 3. Starting with 6.0.24 setHeader() calls with null name or null value are silently ignored. Here is that change: http://svn.apache.org/viewvc?view=revision&revision=832206 Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
