-
Bug
-
Resolution: Done
-
Major
-
2.0.21.Final
-
None
In ServletInitialHandler...
if (!exchange.isDispatched() && !(exchange.getConnection() instanceof MockServerConnection)) { servletRequestContext.getOriginalResponse().responseDone(); servletRequestContext.getOriginalRequest().clearAttributes(); }
There are cases I'm seeing where responseDone() does not always trigger the exchange completion, because the request hasn't cleaned up yet, and exchange completion requires both the request and response to trigger completion. If the request is not completed, by the time the exchange completes, the attributes are already cleared, so the access log exchange completion listener does not see request attributes.
This is frustrating for access logs, because I cannot reliably include servlet request attributes in them and have had to resort to awkward workarounds.
Out of curiosity, why are request attributes cleared anyway?
Feel free to reach out to my @redhat.com address if needed.
- causes
-
UNDERTOW-1722 Memory leak involving request attributes
- Resolved
-
WFLY-13514 Huge memory leak in WildFly
- Closed
- is incorporated by
-
WFCORE-4641 Upgrade Undertow to 2.0.26.Final
- Closed