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 pm Mark Thomas wrote: > 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. > > Providing the calls are in the right order, you should be fine. If you > are using the HTTP APR/native connector you should upgrade to 7.0.11 > since that fixes a bug with Servlet 3.0 async on non-Windows platforms > with that connector (BIO & NIO were fine). > > If you have a simple, test case that demonstrates a bug then please open > a bugzilla entry and add your test case. Please keep it as simple as > possible (ideally a single Servlet) and include the source. > > > The servlet 3.0 spec had the following to say. It seems that my thread may > > not have the "Web Application Environment" but I'm not sure exactly what > > that means: > > In Tomcat JNDI calls may not work. In a full J2EE container, security > context information (that passes current user info to EJB calls) might > not work. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
