https://bz.apache.org/bugzilla/show_bug.cgi?id=60900
Mark Thomas changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://bz.apache.org/bugzilla/show_bug.cgi?id=60900
Darren Maglidt changed:
What|Removed |Added
Resolution|FIXED |---
https://bz.apache.org/bugzilla/show_bug.cgi?id=60900
--- Comment #6 from linbo ---
Tomcat 8.5.3, Tomcat Native 1.2.7
TOmcat 8.5.11 Tomcat Native 1.2.10
Thanks Mark, I will test fixed version when it is available.
--
You are receiving this mail because:
You are the assignee
https://bz.apache.org/bugzilla/show_bug.cgi?id=60900
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
https://bz.apache.org/bugzilla/show_bug.cgi?id=60900
--- Comment #4 from Mark Thomas ---
One additional question. Which version of Tomcat Native are you using?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60900
--- Comment #3 from Mark Thomas ---
I have been unable to reproduce this with 9.0.x or 8.5.x.
Next step is a code review to try and identify a code path that could trigger
this. I don't want to just ignore the null without
https://bz.apache.org/bugzilla/show_bug.cgi?id=60900
--- Comment #2 from linbo ---
Any update? Server closed connection and Client will receive RST due to this
issue.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60900
--- Comment #1 from linbo ---
The similar bug https://bz.apache.org/bugzilla/show_bug.cgi?id=54513
--
You are receiving this mail because:
You are the assignee for the bug.