[Bug 56190] Connection keep-alive not working with asynchronous servlet

https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 --- Comment #11 from Francois-Xavier Bonnet --- Thanks. I just tested. Everything works as expected now. -- You are receiving this mail because: You are the assignee for the bug. --

[Bug 56190] Connection keep-alive not working with asynchronous servlet

https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 Mark Thomas changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug 56190] Connection keep-alive not working with asynchronous servlet

https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 --- Comment #9 from Mark Thomas --- I have the first pass at a fix for this ready. The required changes are minimal but it breaks a lot of unit tests. The unit tests depend on being able to write to the response after the async complete. I

[Bug 56190] Connection keep-alive not working with asynchronous servlet

https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 --- Comment #8 from Mark Thomas --- I've been back and re-read both the Servlet 3.0 and Servlet 3.1 specifications. I don't know where I got the idea from that the response always had to be writable after the call to complete() but that is

[Bug 56190] Connection keep-alive not working with asynchronous servlet

https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 Konstantin Kolinko changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|I

[Bug 56190] Connection keep-alive not working with asynchronous servlet

https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 --- Comment #6 from Francois-Xavier Bonnet --- I did. I know the response is committed when you call AsyncContext.complete() but at this point the response body is fully written. The specification is clear about that: "Completes the asynchr

[Bug 56190] Connection keep-alive not working with asynchronous servlet

https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 Mark Thomas changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug 56190] Connection keep-alive not working with asynchronous servlet

https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 Francois-Xavier Bonnet changed: What|Removed |Added Status|RESOLVED|REOPENED Resoluti

[Bug 56190] Connection keep-alive not working with asynchronous servlet

https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 56190] Connection keep-alive not working with asynchronous servlet

https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 --- Comment #2 from Konstantin Kolinko --- > I get these headers in the response With those headers you have keep-alive enabled (as that is default if nothing else is specified in an HTTP/1.1 response, per HTTP/1.1 specification). So, wha

[Bug 56190] Connection keep-alive not working with asynchronous servlet

https://issues.apache.org/bugzilla/show_bug.cgi?id=56190 --- Comment #1 from Francois-Xavier Bonnet --- I have the same issue with Tomcat 7.0.52 -- You are receiving this mail because: You are the assignee for the bug. - To un