-
Bug
-
Resolution: Done
-
Major
-
None
-
None
In the `websockets-jsr` sub-project there spurious failures in tests `ProgramaticLazyEndpointTest`and `BinaryEndpointTest` when using JDK-17. The errors are something like the following:
[INFO] Running io.undertow.websockets.jsr.test.ProgramaticLazyEndpointTest Error: Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 11.032 s <<< FAILURE! - in io.undertow.websockets.jsr.test.ProgramaticLazyEndpointTest Error: testStringOnMessage(io.undertow.websockets.jsr.test.ProgramaticLazyEndpointTest) Time elapsed: 10.024 s <<< ERROR! java.io.IOException: UT003035: Connection timed out at io.undertow.websockets.jsr.ServerWebSocketContainer.connectToServer(ServerWebSocketContainer.java:332) at io.undertow.websockets.jsr.ServerWebSocketContainer.connectToServer(ServerWebSocketContainer.java:309) at io.undertow.websockets.jsr.test.ProgramaticLazyEndpointTest.testStringOnMessage(ProgramaticLazyEndpointTest.java:108) ...
Note the time taken is 10s which is the timeout used in the test.
- incorporates
-
UNDERTOW-2047 WebSocketClient13TestCase seems to hang
- Closed
- is cloned by
-
JBEAP-23873 [QA](7.4.z) UNDERTOW-2124 - ProgramaticLazyEndpointTest and BinaryEndpointTest failures with JDK-17
- Closed
- is related to
-
UNDERTOW-2134 Prevent testsuite from hanging forever when WebSocketClient13TestCase fails
- Closed
- relates to
-
UNDERTOW-2047 WebSocketClient13TestCase seems to hang
- Closed