https://issues.apache.org/bugzilla/show_bug.cgi?id=53697
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
Without a test case to reproduce the problem there is little the Tomcat
developers can do. It looks like multiple threads are acting on the same socket
at the same time. What I can't tell is if that is intentional, the result of a
Tomcat bug or something the frameworks/app is doing.
The NPE is avoidable in one of the two stack traces provided but I am not yet
sure avoiding it is a good thing (depending on the root cause).
I would add that a test case isn't essential - the Tomcat developers have made
changes in the past for hard to reproduce bugs based purely on the bug
reporters analysis of their code, the Tomcat code and what is going wrong
where. That said, it is also the case that the Tomcat developers have refused
to apply speculative patches that the bug reporter claims fixes the issue that
did not come with an explanation of what the bug was and why the patch fixed
it.
--
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
