Re: Calling AsyncContext.complete() in thread not started by AsyncContext.start()

2011-03-13 Thread Mark Thomas
On 14/03/2011 00:21, Chris wrote: > Thanks for the comments Mark. I've upgraded to 7.0.11 and the issues I was > seeing seem to be gone. > You only mentioned the HTTP APR connecter, but I've noticed a difference for > both HTTP APR and AJP APR. > Does it make sense that the fix also affects AJP?

Re: Calling AsyncContext.complete() in thread not started by AsyncContext.start()

2011-03-13 Thread Chris
Thanks for the comments Mark. I've upgraded to 7.0.11 and the issues I was seeing seem to be gone. You only mentioned the HTTP APR connecter, but I've noticed a difference for both HTTP APR and AJP APR. Does it make sense that the fix also affects AJP? Thanks, Chris On March 13, 2011 06:49:16 p

Re: Calling AsyncContext.complete() in thread not started by AsyncContext.start()

2011-03-13 Thread Mark Thomas
On 13/03/2011 22:33, Chris wrote: > I'm wondering if anyone can comment about whether calling complete() in this > way might cause problems. In general things seem to be working but I'm seeing > behaviour in some situations that leads me to believe requests may not be > properly completed/closed

Calling AsyncContext.complete() in thread not started by AsyncContext.start()

2011-03-13 Thread Chris
I'm using tomcat 7.0.8 on Ubuntu 10.10. I've got a servlet doing Servlet 3.0 asynchronous processing, using HttpServletRequest.startAsync(). The AsyncContext.complete() is later called from a different thread, but it's *not* one that was started by AsyncContext.start(). I'm wondering if anyone