https://issues.apache.org/bugzilla/show_bug.cgi?id=50957
--- Comment #13 from Brad Plies <bpl...@bulliondirect.com> 2011-03-28 16:42:53 EDT --- (In reply to comment #12) > None of those requests use async processing. Unless you explicitly use Servlet > 3.0 async APIs then isAsync() will always return false. In our application we are not explicitly using Servlet 3.0 async so the hypothesis that async() is suspicious in this case is invalid. So as far as deduction goes it one must backtrack to examining how buffers are used and pipelined requests are handled. > At the moment, I'm happy isAsync() is safe. There were issues in the past (bug > 49884) but the re-factoring that fixed that bug means that it should not be > possible for one thread to be reading isAsync() whilst another is changing the > value it returns. isAsync(), I see, uses volatile so maybe it is alright afterall. At least we've managed to deduce a few things that aren't the problem. Thanks for helping. I'll take a look at anything that gets committed and will at least try to run a recent build w/ BIO in an alternate environment. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
