https://issues.apache.org/bugzilla/show_bug.cgi?id=56449
--- Comment #7 from vlcvlc ---
(In reply to Mark Thomas from comment #6)
> (In reply to Mark Thomas from comment #3)
> > What I
> > didn't consider was that the close of the connection rather than the close
> > message may have triggered th
https://issues.apache.org/bugzilla/show_bug.cgi?id=56449
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=56449
--- Comment #5 from vlcvlc ---
(In reply to Mark Thomas from comment #3)
> Thanks for that.
>
> An immediate close was one of the options I considered but I dismissed it as
> I didn't think the close message could have been read that early
https://issues.apache.org/bugzilla/show_bug.cgi?id=56449
--- Comment #4 from vlcvlc ---
(In reply to Mark Thomas from comment #1)
> At the moment, I don't see a code path that could trigger this. The session
> is open when it is created so something must be closing it very quickly. My
> assumptio
https://issues.apache.org/bugzilla/show_bug.cgi?id=56449
--- Comment #3 from Mark Thomas ---
Thanks for that.
An immediate close was one of the options I considered but I dismissed it as I
didn't think the close message could have been read that early. What i didn't
consider was that the close o
https://issues.apache.org/bugzilla/show_bug.cgi?id=56449
--- Comment #2 from Konstantin Preißer ---
Hi Mark,
FYI, I can reproduce the given stack trace if I use a client that sends an
initial Websocket Request but immediately closes the TCP connection. E.g., when
running the following Java code
https://issues.apache.org/bugzilla/show_bug.cgi?id=56449
--- Comment #1 from Mark Thomas ---
At the moment, I don't see a code path that could trigger this. The session is
open when it is created so something must be closing it very quickly. My
assumption is that there must be an error path trigg
