Dan Checkoway <dchecko...@gmail.com> wrote: >Mark, > >I wanted to let you know that 7.0.14 (I dl'd the official release this >morning) changed the behavior slightly, but it didn't fix the bug. The >behavior I'm seeing now is: > >response.sendError - seems to close the connection immediately (doesn't >wait >to time out like 7.0.12 did), but you get no headers or content of any >kind. > >response.sendRedirect - no change, still just times out, and you get no >headers or content of any kind. > >Should I open a ticket for this? It's not a showstopper for me, since >I can >work around it with .setStatus and .setHeader, but I do think it's a >legit >bug...unless you think I've missed something about AsyncContext usage >and >I'm doing something wrong. > >Again, my easily reproducible test case is here: > >https://github.com/dcheckoway/async-test > >Thanks, >Dan > >On Thu, May 12, 2011 at 1:00 PM, Dan Checkoway <dchecko...@gmail.com> >wrote: > >> Ah, excellent. Glad to know I wasn't on crack. :-) Thanks for the >quick >> reply! >> >> Dan >> >> >> On Thu, May 12, 2011 at 12:51 PM, Mark Thomas <ma...@apache.org> >wrote: >> >>> On 12/05/2011 17:33, Dan Checkoway wrote: >>> > Hello, >>> > >>> > I recently started working with Servlet 3.0 async stuff with >Tomcat >>> 7.0.12, >>> > and I bumped into what may be a serious bug. Or it may be that >I'm just >>> > doing something dumb. :-) >>> > >>> > For some reason, response.sendRedirect and response.sendError are >not >>> > producing expected behavior when using an AsyncContext. The async >>> request >>> > completes normally, and everything looks hunky dory on the server >side, >>> but >>> > the client never gets ANY response from the server. It appears >that >>> Tomcat >>> > simply times out after the default 10 seconds and closes the >connection. >>> No >>> > headers are returned, no content, nothing. I've confirmed with >thread >>> dumps >>> > that the server isn't stuck. >>> > >>> > Yet...if you use response.setStatus and response.setHeader >instead, it >>> works >>> > absolutely fine. The client gets the response every time. >>> > >>> > I put together a very simple test that isolates the issue >reliably: >>> > https://github.com/dcheckoway/async-test >>> > >>> > See the README in there for details. >>> > >>> > Please let me know if I've missed something simple! I'm >relatively new >>> to >>> > Servlet 3.0... >>> >>> Similar to a known issue that has already been fixed. >>> >>> The fix is in 7.0.14. The official 7.0.14 release should be >available >>> later tonight. If you are in a hurry, you can get the release >candidate >>> from here: >>> http://people.apache.org/~markt/dev/tomcat-7/v7.0.14/ >>> >>> Mark >>> >>> >>> >>> >--------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >>> >>
Yes, please open a bugzilla issue for this. Cheers, Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
