Summary: | Request body exposed as part of other request | ||
---|---|---|---|
Product: | Tomcat 7 | Reporter: | Abishek <abishek.bb> |
Component: | Connectors | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | abishek.bb |
Priority: | P2 | ||
Version: | 7.0.42 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
Abishek
2013-07-26 08:08:34 UTC
In the significant majority of cases this turns out to be an application issue not a Tomcat one. Please debug this on the Tomcat users mailing list. Feel free to re-open this issue if you reach either of the following points: - you have a repeatable test case that demonstrates the issue - you have identified a code path within Tomcat that could lead to request mix-up (In reply to Mark Thomas from comment #1) > In the significant majority of cases this turns out to be an application > issue not a Tomcat one. Please debug this on the Tomcat users mailing list. > > Feel free to re-open this issue if you reach either of the following points: > > - you have a repeatable test case that demonstrates the issue > > - you have identified a code path within Tomcat that could lead to request > mix-up Thanks Mark. I will check my application. I did not get any clue though. Let me give you more info. Request body of requests using asynchronous servlets are mixing up with jersey API requests. Should I close request using async servlets somewhere ? No clue whatsoever. Please help me. |