Hi, Thanks for your feedbacks. I noticed the issue I described do not occur on my local or integration environment. I still try to figure out how to reproduce this in an environment I can easely update to the latest tomcat version.
Although it may not occur in latest release. Could you give me an input on what are the consequences of the behaviour I described ? Thanks, Thomas 2016-09-29 9:41 GMT+02:00 Violeta Georgieva <violet...@apache.org>: > Hi, > > 2016-09-29 10:14 GMT+03:00 Thomas Boniface <tho...@stickyads.tv>: > > > > The tomcat version is 7.0.64. > > I would recommend you to verify the behaviour against the latest Tomcat 7 > (7.0.72). > We have changes in the async processing since 7.0.64. > http://tomcat.apache.org/tomcat-7.0-doc/changelog.html > > Regards, > Violeta > > > Thomas > > > > 2016-09-28 22:43 GMT+02:00 Christopher Schultz < > ch...@christopherschultz.net > > >: > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA256 > > > > > > Thomas, > > > > > > On 9/28/16 11:55 AM, Thomas Boniface wrote: > > > > Hi, > > > > > > > > When a client calls an asynchronous servlet and closes the > > > > connection a java.io.IOException: Broken pipe is catched by Tomcat > > > > level when the webapp tries to write to the socket. > > > > > > > > This exception is not transmited to the webapp level but it seems > > > > the request has been recycled (all content is reinitialised), in > > > > such a case it impossible for the webapp to retrieve the > > > > AsyncContext from the HttpServletRequest making the AsyncContext > > > > complete call impossible. > > > > > > > > Activating the tomcat logging for AsyncContext > > > > (org.apache.catalina.core.AsyncContextImpl.level = FINE) shows the > > > > recycle method is called but not the complete method, what seems to > > > > confirm my assumption. In a use case were the client waits for the > > > > response, I can see both complete and recycle are called. > > > > > > > > My question is, what is the impact of the complete not being called > > > > on the AsyncContext, is the socket cleaned up properly ? > > > > > > Tomcat version? > > > > > > - -chris > > > -----BEGIN PGP SIGNATURE----- > > > Comment: GPGTools - http://gpgtools.org > > > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > > > > > iQIcBAEBCAAGBQJX7CtcAAoJEBzwKT+lPKRYwekP/R1wirv0g7wJ3uR1Xk4mYIQo > > > jPUYBirzVcewTWrDUpOe4BdXUBzgk7zDVrOsWU9PGlc0Prwik9YHeFWlG9ItxeEs > > > 0ZJ0vJ1z6Od0KsxN6E8KobsE3rQu+td1Mh7d0g76zbHQKiLmrJNb8/hGuHVQr9Fd > > > M597bec0JYiQSXU+8/SMErx/bdoA8HcApaeJpnl/RuCLfYwQ5ZSS/e0SCuSqMi1W > > > bEU0vj0pBfK6h1WuweCRoBL5Shxa2XBpbc8nlPgb7IHNlQ15dwlD10nnuYDLb7DR > > > VmOYEx2fmynZ/fOajfTsHoWUpoHjK47vMjtLUpIXARN8LY6tR2A2iUqJ6gXlM+QL > > > gNRkucxkI3RSV3U7ipx7y5IJTglFC7uAyFlJpPLx8gLhGWSUz+q46lDr+332kF5x > > > VU7rKLY/3RcSJG0ZLfIzPly5tz8wssMvwu94nI8lQb4SweEJDa6cT5Z8aUUTFaf6 > > > kjy34jSgsi6QyN+NK9WKapdDNzvIo1X18zK2CqfDSeyBsgprU62o1P8R/BxIiM9f > > > YAnK98kPtmmKyJHcS7+fBngO1/TZvsdGlYj+cXcnCNi0Fnp50WKlHOPb6wcZo5q5 > > > lcpLkwj4izmdgW8rONjMDAZj3gal7OKw0WQ/srU6XIfUa1kgR0NAtb7YQGvHJA5g > > > ljFdLIuRnMu+43OsbSKC > > > =zrQ5 > > > -----END PGP SIGNATURE----- > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > > > >
