Spurious websocket close errors #668
Labels
Comments
|
Full stack trace: |
|
Is there any update on this issue? when the client side shuts down the connection (it seems?). |
|
I also have this issue, and would love an answer. Is there any work being done on the braze connector? |
|
If you can point me into a direction I'll even take a look |
|
I'm not actively working on it. A reliable reproduction would help a lot. The Adding logging to the |
|
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 meet the same problem, but package name different. http4s-version: 0.23.6 |
|
I also run into this, but only when trying to run my server val server: Resource[IO, Server[IO]] =
BlazeServerBuilder(ec)(ioConcurrentEffect, timer)
.bindHttp(8080, "localhost")
.withHttpApp(httpAppWithLoggers)
.resource
val client: Resource[IO, Client[IO]] =
BlazeClientBuilder(ec)(ioConcurrentEffect)
.resource
.map(c => client.middleware.RequestLogger(logHeaders = true, logBody = true)(c))http4s:
"org.specs2" %% "specs2-core" % "4.3.4"
"org.typelevel" %% "cats-core" % "1.3.1"
"org.typelevel" %% "cats-effect" % "1.0.0" |
geminicaprograms
added a commit
to softwaremill/adopt-tapir
that referenced
this issue
Oct 12, 2022
There issue with non-deterministic EOF is obsevable by others but so far there is no good explanation (or test method) given (see [1]) therefore for the time being we are switching to vertx http server. TODO: * `OPTIONS` request is not accepted and results in `405 Method Not Allowed` therefore UI is not able to talk to the server but calling `curl` works * at the moment one cannot customise the logs hence they are not displayed when the server is started Verifies #49 [1] http4s/blaze#668
geminicaprograms
added a commit
to softwaremill/adopt-tapir
that referenced
this issue
Oct 12, 2022
There issue with non-deterministic EOF is observable by others but so far there is no good explanation (or test method) given (see [1]) therefore for the time being we are switching to vertx http server. TODO: * `OPTIONS` request is not accepted and results in `405 Method Not Allowed` therefore UI is not able to talk to the server but calling `curl` works * at the moment one cannot customise the logs hence they are not displayed when the server is started Verifies #49 [1] http4s/blaze#668
geminicaprograms
added a commit
to softwaremill/adopt-tapir
that referenced
this issue
Oct 12, 2022
There issue with non-deterministic EOF is observable by others but so far there is no good explanation (or test method) given (see [1]) therefore for the time being we are switching to vertx http server. TODO: * `OPTIONS` request is not accepted and results in `405 Method Not Allowed` therefore UI is not able to talk to the server but calling `curl` works * at the moment one cannot customise the logs hence they are not displayed when the server is started Verifies #49 [1] http4s/blaze#668
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
http4s-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:
It seems to have some impact on the connecting client as about 1 out of 20 jmeter results end up red.
The text was updated successfully, but these errors were encountered: