Only found https://bz.apache.org/bugzilla/show_bug.cgi?id=59261 which doesn't mean this code would be invalid
Also if you add a listener eagerly you will have the start event and loose all "end" (completed, timeout etc...) ones. This doesn't sound very reliable. Can you point me out the related issue please? Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2016-05-17 12:26 GMT+02:00 Mark Thomas <ma...@apache.org>: > On 17/05/2016 11:24, Romain Manni-Bucau wrote: > > Hi guys, > > > > on 8.5.2 this code doesn't work anymore (in a valve): > > > > if (!request.isAsync()) { > > > > getNext().invoke(request, response); > > > > } else { > > request.getAsyncContext().addListener(...); > > getNext().invoke(request, response); > > } > > > > Issue is isAsync() = true but getAsyncContext() throws an exception since > > isAsyncStarted() = false. > > > > Was it intended? > > Yes. It is in the change log. > > Mark > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
