-
Notifications
You must be signed in to change notification settings - Fork 596
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Processor actor terminated abruptly on HTTPs connections (akka 2.4.12, akka-http 2.4.11) #497
Comments
This error message is probably harmless. The reason it occurs is that when an ActorSystem is shutdown it stops all its actors. The streaming infrastructure relies on those actors and then complains that something has shutdown the actors. This happens in particular with the connection pool actors as these streams need to be kept alive for future requests. Still, it's unfortunate, that these expected errors are logged verbosely in the console (we are also seeing them in tests). Here's a related ticket from akka to improve the situation: akka/akka#18747 |
It's also somewhat related with #450. |
I have also stumbled upon this. Repro at https://github.com/arturaz/akka-http-https-bug-repro |
We are also seeing this issue. It's harmless as the code executes but really confusing to the users of our CLI which uses akka-http as they think there's been an error when nothing is wrong. |
We are using Await.result(httpExt.shutdownAllConnectionPools(), shutDownWaitTime)
Await.result(actorSystem.terminate(), shutDownWaitTime) |
I created #907 to track further improvements in the shutdown process. Closing here. |
Undeterministically generates a harmless error message from Akka in the console (akka/akka-http#497). Future work: disable this message.
I posted on akka-user, but since I believe it might be a bug, I am opening an issue for that.
The problem seems to be that when performing
HTTPS
queries using a connection pool, shutting down the actor system raises the following error:An example of simple code that reproduces the problem (replace the
https
prefix byhttp
in theuri
field to make the problem disappear)An example of code that does not exhibit the problem (no connection pool)
The text was updated successfully, but these errors were encountered: