...
- com/sun/ts/tests/websocket/ee/javax/websocket/session/WSClient.java#setTimeout1Test
- com/sun/ts/tests/websocket/spec/servercontainer/addendpoint/WSClient.java#setTimeout1Test
- This looks caused by the client side and a race condition of some sort on the session open state, if I add debug information in WsFrameClient.processSocketRead, the issue becomes very hard to reproduce. I propose adding if (wsSession.isOpen()) around the processInputBuffer(); in WsFrameClient.processSocketRead, this explicitly avoids writing any new input data after the session timeout.
A further 15 test failures caused by Tomcat bugs have been fixed
...