[Bug 63931] The remote endpoint was in state [TEXT_FULL_WRITING] which is an invalid state

https://bz.apache.org/bugzilla/show_bug.cgi?id=63931 Mark Thomas changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 63931] The remote endpoint was in state [TEXT_FULL_WRITING] which is an invalid state

https://bz.apache.org/bugzilla/show_bug.cgi?id=63931 --- Comment #9 from Mark Thomas --- That you aren't seeing any exceptions before this one is not what I would expect. We have a unit test (TestWebSocketFrameClient) that can be fairly easily tweaked to simulate this scenario - a server sending

[Bug 63931] The remote endpoint was in state [TEXT_FULL_WRITING] which is an invalid state

https://bz.apache.org/bugzilla/show_bug.cgi?id=63931 --- Comment #8 from Saurav Singh --- Hey Mark! Sorry if my tone of comment #6 sounds something different which wasn't meant to be its just being impatient. When i raised the bug with Apche i didn't think of cost involved; its apache foundation

[Bug 63931] The remote endpoint was in state [TEXT_FULL_WRITING] which is an invalid state

https://bz.apache.org/bugzilla/show_bug.cgi?id=63931 --- Comment #7 from Mark Thomas --- >From the tone of comment #6 you appear to have forgotten that everyone here is a volunteer, providing you with help and assistance (at no cost) to use the software that you have been given (also at no cost).

[Bug 63931] The remote endpoint was in state [TEXT_FULL_WRITING] which is an invalid state

https://bz.apache.org/bugzilla/show_bug.cgi?id=63931 --- Comment #6 from Saurav Singh --- Can I expect any help from apahe team to understand what's wrong going on? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 63931] The remote endpoint was in state [TEXT_FULL_WRITING] which is an invalid state

https://bz.apache.org/bugzilla/show_bug.cgi?id=63931 --- Comment #5 from Saurav Singh --- You can see just now got same issue after raising the bug ticket: 2019-11-18T15:29:29,041 [tainer#0-1] co.ea.ex.no.tr.we.WebSocketServerHandler ERROR: o.tr.we.WebSocketServerHandler(dToSession: 525) Encoun

[Bug 63931] The remote endpoint was in state [TEXT_FULL_WRITING] which is an invalid state

https://bz.apache.org/bugzilla/show_bug.cgi?id=63931 --- Comment #4 from Saurav Singh --- So I am working on Spring boot websocket which has method a afterConnectionClosed(final WebSocketSession session, final CloseStatus status) throws Exception that I have overriden on same handler class howeve

[Bug 63931] The remote endpoint was in state [TEXT_FULL_WRITING] which is an invalid state

https://bz.apache.org/bugzilla/show_bug.cgi?id=63931 --- Comment #3 from Mark Thomas --- You should see a call to onClose() before this happens. You should also see an IOException in the thread writing the message. One thing I think Tomcat could improve on, is preventing applications trying to w

[Bug 63931] The remote endpoint was in state [TEXT_FULL_WRITING] which is an invalid state

https://bz.apache.org/bugzilla/show_bug.cgi?id=63931 --- Comment #2 from Saurav Singh --- Hey Mark Thanks for response. 1. Once you see the exception, do all subsequent attempts to write a message trigger that exception? Answer --> Yes It does try to write message and trigger that excpetion and

[Bug 63931] The remote endpoint was in state [TEXT_FULL_WRITING] which is an invalid state

https://bz.apache.org/bugzilla/show_bug.cgi?id=63931 Mark Thomas changed: What|Removed |Added OS||All --- Comment #1 from Mark Thomas ---