https://bz.apache.org/bugzilla/show_bug.cgi?id=65780
Remy Maucherat <r...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #4 from Remy Maucherat <r...@apache.org> ---
(In reply to Mark Thomas from comment #3)
> I'm leaning towards resolving this one as WONTFIX. I agree writing thread
> safe code is hard and can be tedious but the NPE is signalling there is an
> application bug. I'd rather Tomcat threw the NPE and developer made the
> choice to fix the bug or swallow the NPE rather than Tomcat hiding the bug.
Other places in Request/ResponseFacade have a null check and throw an ISE with
a good error message, so I decided to do it there too. However, I'm also not ok
with swallowing the problem and pretending all is well.
> The ServletOutputStream Javadoc needs to be changed. There is no way the
> container can tell if a write will succeed or not.
ServletInputStream.isReady is more explicit that this is about blocking rather
than a guarantee that the IO operation will return without any error.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
