You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling DefaultAsyncServerResponse.writeAsync() unconditionally creates a new AsyncWebRequest and installs it on the WebAsyncManager, even when one is already present for the current request. The functional web framework can do such a thing when returning a ServerResponse.async(future) from a HandlerFunction; the HandlerFunctionAdapter does install an async web request already.
This means that the async timeout configured at the application level is ignored and instead we are falling back to the Servlet container default.
This was probably missed so far because the future backing the response could be already completed by the time writeAsync() runs. This becomes more visible in the case of GraphQL operations for long running operations (hence the virtual threads remark in the original issue).
Activity
github-actions commentedon Sep 8, 2026
Fixed via 3c6b001
Reuse existing async timeout in DefaultAsyncServerResponse
Add implementation note in DefaultAsyncServerResponse