Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
TimeoutException: Timeout of 30 seconds triggered. Killing pipeline.
See original GitHub issueI get the following error message in the log with http4s v0.20.0-M2. This doesn’t occur with 0.18.19. Not sure if this is related to http4s client or server. The error message looks the same as with #2156, but this still happens with M2.
2018-11-06 21:41:53.255 [blaze-selector-0-2] ERROR o.h.blaze.channel.nio1.NIO1HeadStage - Abnormal NIO1HeadStage termination
java.util.concurrent.TimeoutException: Timeout of 30 seconds triggered. Killing pipeline.
at org.http4s.blaze.pipeline.stages.TimeoutStageBase$$anon$1.run(TimeoutStageBase.scala:29)
at org.http4s.blaze.util.Execution$$anon$3.execute(Execution.scala:66)
at org.http4s.blaze.util.TickWheelExecutor$Node.run(TickWheelExecutor.scala:261)
at org.http4s.blaze.util.TickWheelExecutor$Bucket.checkNext$1(TickWheelExecutor.scala:193)
at org.http4s.blaze.util.TickWheelExecutor$Bucket.prune(TickWheelExecutor.scala:200)
at org.http4s.blaze.util.TickWheelExecutor.go$3(TickWheelExecutor.scala:153)
at org.http4s.blaze.util.TickWheelExecutor.org$http4s$blaze$util$TickWheelExecutor$$cycle(TickWheelExecutor.scala:156)
at org.http4s.blaze.util.TickWheelExecutor$$anon$1.run(TickWheelExecutor.scala:55)
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (13 by maintainers)
Top Results From Across the Web
http4s/http4s - Gitter
TimeoutException : Timeout of 30 seconds triggered. Killing pipeline. at org.http4s.blaze.pipeline.stages.
Read more >[JIRA] (JENKINS-40839) pipeline timeout doesn't kill the job
We have hit the outer 30min timeout just after building the image but before starting the container. But jenkins failed to kill the...
Read more >c# - Timeout expired. The timeout period elapsed prior to ...
This type of timeout can have three causes; There's a deadlock somewhere. The database's statistics and/or query plan cache are incorrect.
Read more >SQL SERVER - Timeout expired. The timeout period elapsed ...
NET application is generally 30 seconds. If any request is in progress and it couldn't complete within the timeout period, we would again ......
Read more >Azure Functions: Extend Execution Timeout Past 5 Minutes
* Regardless of the Function App Timeout configuration, 230 seconds is the maximum amount of time that an HTTP Triggered function can take...
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 Free
Top 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
Nope, we didn’t deprecate it properly. Sorry for the problem. #2285 should prevent it from happening to anyone else.
It doesn’t happen on
Ok("pong")but it does onOk(). That’s a big clue.