Right on. Thank you both, Mark and Niki.
-Igor.
On Sun, Sep 1, 2013 at 3:00 AM, Mark Thomas wrote:
> On 31/08/2013 02:40, Igor Urisman wrote:
> > That's correct. I call close() inside onOpen(). You correctly call
> > onClose() on the endpoint as well, so my code is happy. But a thread of
>
On 31/08/2013 02:40, Igor Urisman wrote:
> That's correct. I call close() inside onOpen(). You correctly call
> onClose() on the endpoint as well, so my code is happy. But a thread of
> yours crashes milliseconds later. I have no problem changing my code to
> call close() after onOpen() returns,
That's correct. I call close() inside onOpen(). You correctly call
onClose() on the endpoint as well, so my code is happy. But a thread of
yours crashes milliseconds later. I have no problem changing my code to
call close() after onOpen() returns, of course. But if you insist on this
semantics,
On Sat, Aug 31, 2013 at 12:33 AM, Igor Urisman wrote:
> Dear all,
>
> Getting the following exception with none of my code on the stack:
>
> SEVERE: Error reading request, ignored
> java.lang.IllegalStateException: The WebSocket session has been closed and
> no method (apart from close()) may be c
Dear all,
Getting the following exception with none of my code on the stack:
SEVERE: Error reading request, ignored
java.lang.IllegalStateException: The WebSocket session has been closed and
no method (apart from close()) may be called on a closed session
at org.apache.tomcat.websocket.WsSess
