-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
ReadTimeoutStreamSourceConduit.checkExpired uses a bad time parameter in its readTimedOut exception:
private void checkExpired() throws ReadTimeoutException { synchronized (this) { if (expired) { throw UndertowMessages.MESSAGES.readTimedOut(System.currentTimeMillis()); } } }
This results in a debug message that doesn't make sense with an incorrect timeout duration:
DEBUG [io.undertow.request.io] (default I/O-14) UT005013: An IOException occurred: org.xnio.channels.ReadTimeoutException: UT000199: Read timed out after 1638571000771 milliseconds.
- is incorporated by
-
UNDERTOW-2125 ReadTimeoutStreamSourceConduit expires when connection is closed
- Closed
-
WFCORE-6057 Upgrade Undertow to 2.3.0.Final (CVE-2022-2764)
- Closed
-
WFLY-17017 Upgrade Undertow to 2.3.0.Beta1
- Closed
-
WFCORE-6056 Upgrade Undertow to 2.3.0.Beta1
- Closed