]
Stuart Douglas commented on WFLY-3962:
--------------------------------------
The isssue is that isAsyncStarted() was still returning true even after complete() had
been called. In the same this resulted in a listener being added after the context had
already completed, and as a result it was not called.
This has been fixed in Undertow 1.2 and 1.1 branches.
onComplete for async listeners not always called
------------------------------------------------
Key: WFLY-3962
URL:
https://issues.jboss.org/browse/WFLY-3962
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 8.0.0.Final, 8.1.0.Final
Reporter: Heiko Rupp
Assignee: Stuart Douglas
I have a servlet filter that does
chain.doFilter(requestWrapper, responseWrapper);
if (request.isAsyncStarted()) {
asyncListener =
request.getAsyncContext().createListener(JsonPAsyncListener.class);
request.getAsyncContext().addListener(asyncListener, requestWrapper,
responseWrapper);
}
And (sometimes) this works well so that the onComplete() method of the listener is
called.
But this does not happen always. In some (repeatable) condition none of the callback
methods in my AsyncListener are called.
I was first thinking that the servlet (resteasy) behind chain.doFilter() is so fast that
it completes
before I can add the listener.
But then I tried adding a Thread.sleep() in the RE code which did not change anything.
Similar when I do a startAsync() and add the listener before calling chain.doFilter()
This happens both on Wfly 8.0 and 8.1
Basically it boils down that if the "backend" uses
Futures.immediateFuture(result) , onComplete is not called.
I have created a as small as possible war file + a read me on how to drive that via
curl.
See
https://github.com/pilhuhn/misc/tree/master/web-goo
I just added 2 examples to the readme file that show that if no
wrapping by the filter is requested, the resteasy code works with
both Futures.immediate... and Futures.transform(...)