Spurious websocket close errors
See original GitHub issuehttp4s-version: 0.20.10 java-version: 11.0.4 (adoptopenjdk) scala: 2.12.9 server backend: blaze (whatever version comes with http4s 0.20.10)
When running jmeter against a websocket endpoint I’m getting these kinds of errors every now and then:
2019-09-02T13:56:30,040Z [scala-execution-context-global-14] ERROR o.h.b.websocket.Http4sWSStage - Error closing Web Socket
fs2.CompositeFailure: Multiple exceptions were thrown (2), first org.http4s.blaze.pipeline.Command$EOF$: EOF
… further stack-trace of FS2/Monix stuff
It seems to have some impact on the connecting client as about 1 out of 20 jmeter results end up red.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
WebSockets - Handling Errors
WebSockets - Handling Errors, Once a connection has been established between the client and the server, an open event is fired from the...
Read more >NIOSSL: spurious uncleanShutdown error - Swift Forums
my websocket implementation yields an error to its AsyncThrowingStream<T, Failure>.Continuation whenever the errorCaught(context:error:) method ...
Read more >WebSockets error on close - Stack Overflow
I am new to WebSockets and was trying out an example I found online. The example simple has the server parrot back whatever...
Read more >Both sides - websockets 10.4 documentation
If the corresponding Pong frame isn't received within ping_timeout seconds, the connection is considered unusable and is closed with code 1011. This ensures ......
Read more >WebSocket Error - Connection is already closed. - Qxf2 BLOG
I received this error when working on an application that involved a WebSocket connection. The Websocket handshake between the client and ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
From what I can tell the connection to the client is severed.
I’ll take a look into the TicketWheelExecutor and let you know what I’ll find out. I’ll also put together steps to reproduce the problem, it happened to me from a stock test of the demo echo server from what I remember, so it shouldn’t be too difficult to reproduce.
I also run into this, but only when trying to run my server
Resource
s sequentially with theorg.specs2
sequential
keyword:http4s:
0.20.23
server backend: blaze java:11.0.14
(Ubuntu Java) scala:2.12.14
sbt:sbt 1.6.1
build.sbt
: