I am using Asynchronous servlet with Tomcat 7 and also jersey APIs in my application. I see request body of one request forming a part of other request which happens to be jersey API. And in turn, the jersey API request becomes a bad request and returns 405. This is blocker for my work as I could not use my application. Please let me know if there needs to be a configuration change. Or Please let me know if its a bug in tomcat. I see similiar bugs reported which say request body exposed in some tomcat versions. Then I took latest version(7.0.42) where it is fixed. But I see the issue in that version. Please let me know if you need more info.
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.