-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
28.0.1.Final
-
None
https://issues.redhat.com/browse/WFLY-14980 changed Undertow's default read/write timeouts to 90 seconds. This causes WebSockets to get disconnected after 90 seconds if both sides are not sending messages. It probably also breaks server-sent event streams since the client can't send anything after the initial request, though I have not tested that.
WebSockets and SSE streams should therefore be exempted from read/write timeouts, or at least have independent timeout settings.
Workaround: set read-timeout and write-timeout to 0 on the http(s)-listener in the Undertow subsystem. This restores the old behavior.
- blocks
-
JBEAP-28281 (8.0.z) UNDERTOW-2333 - Undertow read/write timeout should not apply to WebSockets or SSE
- Verified
- is cloned by
-
UNDERTOW-2333 Undertow read/write timeout should not apply to WebSockets or SSE
- Closed
- is duplicated by
-
WFLY-19861 Add Websocket specific I/O timeouts
- Resolved