Summary: | org.apache.tomcat.util.net.AprEndpoint$Poller.run throws java.lang.NullPointerException | ||
---|---|---|---|
Product: | Tomcat 8 | Reporter: | linbo <llbgurs> |
Component: | Connectors | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 8.5.11 | ||
Target Milestone: | ---- | ||
Hardware: | PC | ||
OS: | Linux | ||
Attachments: | server.xml configure file |
Description
linbo
2017-03-22 01:33:54 UTC
The similar bug https://bz.apache.org/bugzilla/show_bug.cgi?id=54513 Any update? Server closed connection and Client will receive RST due to this issue. 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 understanding what is going on. One additional question. Which version of Tomcat Native are you using? I was looking at possible triggers for this around concurrent timeout/close and new data arriving. While I was doing that I found and fixed some edge cases that made this bug easier to trigger. I have therefore fixed this bug too. Fixed in: - trunk for 9.0.0.M19 onwards - 8.5.x for 8.5.13 onwards 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. The fix for Bug 60900 (https://bz.apache.org/bugzilla/show_bug.cgi?id=60900) should also be applied to Tomcat 7.0.x. The issue still exists in 7.0.81, as the wrapper assigned on AprEndpoint.java:1898 is not checked for null prior to reference on AprEndpoint.java:1906. I've back-ported the NPE fix to: - 8.0.x for 8.0.47 onwards - 7.0.x for 7.0.82 onwards I didn't back-port the edge case fixes as the refactoring in 8.5.x means the associated code is different (e.g. it has Comet handling) and I didn't want to risk triggering a regression. |