Summary: | AJP connector sends GET BODY CHUNK when reading after response closed | ||
---|---|---|---|
Product: | Tomcat 5 | Reporter: | James Roper <jroper2> |
Component: | Connector:AJP | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | clint.morgan |
Priority: | P2 | ||
Version: | 5.5.23 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
James Roper
2010-10-31 23:27:02 UTC
Thanks for the report. Which version of mod_jk and which config are you using? The version of mod_jk is 1.2.28 on CentOS 5.4. If you are unable to reproduce this issue, let me know and I'll do more investigations to reproduce it on my side, I'll see if I can reproduce it on later versions of Tomcat and I'll attach tcpdump logs etc. I haven't done that yet because the only logs and environment that I have handy are a production environment, and the logs contain sensitive information, but I'm hoping my description so far is adequate. I've also hit this issue in tomcat 6.0.26 and 7.0.4. This has been using an in-house version of the AJP client (webserver-side). Our symptoms were the same, and we had been working around by disabling connection sharing across requests. Following James' advice, I've removed the possibility for a servlet-side read from the request after the response has been closed. This has resolved the issue of us. Fixed in 7.0.x and will be included in 7.0.9. An attempt to read from the request once the response has been will trigger an exception. I'll also propose back-ports for 6.0.x and 5.5.x Fixed in 6.0.x and will be included in 6.0.33 onwards. This has been fixed in 5.5.x and will be included in 5.5.34 onwards. |