Re: Async servlet and request recycling

2016-11-02 Thread Mark Thomas
On 02/11/2016 08:51, Thomas Boniface wrote: > I'm glad this was useful in the end. > > Could you send the link to the corresponding issue ? I'd be interesting to > read the commit for the fix and known the tomcat versions this will be > pushed to. There is no issue. In terms of the commits,

Re: Async servlet and request recycling

2016-11-02 Thread Thomas Boniface
I'm glad this was useful in the end. Could you send the link to the corresponding issue ? I'd be interesting to read the commit for the fix and known the tomcat versions this will be pushed to. Thanks 2016-11-01 11:08 GMT+01:00 Mark Thomas : > On 25/10/2016 09:59, Mark Thomas

Re: Async servlet and request recycling

2016-11-01 Thread Mark Thomas
On 25/10/2016 09:59, Mark Thomas wrote: > Thanks for this. > > While I haven't had a chance to look into this, there is enough > information here to justify opening a bug report. That has the added > advantage that it won't get forogtten. I've found the time to look at this. There was a bug.

Re: Async servlet and request recycling

2016-10-25 Thread Mark Thomas
Thanks for this. While I haven't had a chance to look into this, there is enough information here to justify opening a bug report. That has the added advantage that it won't get forogtten. Mark On 18/10/2016 09:55, Thomas Boniface wrote: > Just a small correction, the callback was a bit weird.

Re: Async servlet and request recycling

2016-10-18 Thread Thomas Boniface
Just a small correction, the callback was a bit weird. The correct one is below (but that doesn't impact the behavior of the scenario) @Override public void completed(HttpResponse result) { try { try { Thread.sleep(200); } catch (InterruptedException e) {

Re: Async servlet and request recycling

2016-10-18 Thread Thomas Boniface
I think I managed to narrow things down a bit. I managed to reproduced locally the issue (it's not occuring 100% of the time but it appears after a very few attempt for me). I created a really basic webapps : package stickyads.tv; import org.apache.http.HttpResponse; import

Re: Async servlet and request recycling

2016-10-10 Thread Mark Thomas
On 10/10/2016 15:47, Thomas Boniface wrote: > Hello, > > I have managed to test this use case on the server revealing the issue with > the latest tomcat release (7.0.72). I still can observe the issue on > catalina.out side: a broken pipe exception pops up and a recycle is shown > for the async

Re: Async servlet and request recycling

2016-10-10 Thread Thomas Boniface
Hello, I have managed to test this use case on the server revealing the issue with the latest tomcat release (7.0.72). I still can observe the issue on catalina.out side: a broken pipe exception pops up and a recycle is shown for the async context but no complete. Oct 10, 2016 4:41:07 PM

Re: Async servlet and request recycling

2016-10-03 Thread Thomas Boniface
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

Re: Async servlet and request recycling

2016-09-29 Thread Violeta Georgieva
Hi, 2016-09-29 10:14 GMT+03:00 Thomas Boniface : > > 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

Re: Async servlet and request recycling

2016-09-29 Thread Thomas Boniface
The tomcat version is 7.0.64. Thomas 2016-09-28 22:43 GMT+02:00 Christopher Schultz : > -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

Re: Async servlet and request recycling

2016-09-28 Thread Christopher Schultz
-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. >