akka/akka-http

Use new shutdown hooks in Akka 2.5 to prevent AbruptTerminationException in Http infrastructure

Open

#907 opened on Feb 27, 2017

View on GitHub
 (5 comments) (10 reactions) (0 assignees)Scala (1,311 stars) (598 forks)batch import
1 - triagedhelp wantedt:core

Description

There are already some hook phases pre-allocated for exactly this purpose.

All active components should be shutdown in the hook:

  • Http().shutdownAllConnectionPools
  • Also introduce some infrastructure to track open server bindings and shut them down.

Contributor guide

Tech stack
scala
Domain
backendapiperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
ScalaAkkaAkka HTTP internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine the existing pre allocated hook phases in Akka 2.5 that are intended for shutdown. Implement a shutdown hook that calls `Http().shutdownAllConnectionPools` and introduces infrastructure to track open server bindings to shut them down gracefully. Review the issue comments for any additional context or constraints. Files to modify likely reside in the akka http core module, possibly in `Http.scala` or similar.