Hi Peter, thanks for reporting this here. It looks like a regression in Undertow.
swd847 could you please look at it? Looking briefly to the changes between 2.0.11.Final and 2.0.12.Final , there are two commits that might be related to this change of behavior:
If this is really a bug, then this is quite a serious regression, right?
I updated my sample on github and created a branch 'undertow-1455-workaround'.
What are your expectations, if I call AsyncContext.complete() in the onError() callback should I receive the onComplete() callback as well?
In my modified sample the ErrorHandlingAsyncListener.onError() calls AsyncContext.complete() as suggested, but the listener for onComplete() gets not called by container.
Thanks for your help,
You are right, only workaround I see now is to "Move cleanup onComplete() code to onError() method"
Thanks for the feedback. Sure I could call cleanup code in onError() as workaround in the meantime, until UNDERTOW-1455 gets fixed.