tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Kolinko <>
Subject Re: Calling flushBuffer() in TOMCAT 6.0.20 returning NullPointerException.
Date Fri, 19 Feb 2010 19:22:15 GMT
2010/2/19 Pid <>:
> On 19/02/2010 16:49, Christopher Schultz wrote:
>> 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)

(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:

Best regards,
Konstantin Kolinko

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message