All Downloads are FREE. Search and download functionalities are using the official Maven repository.

play.reference-overrides.conf Maven / Gradle / Ivy

The newest version!
# Copyright (C) from 2022 The Play Framework Contributors , 2011-2021 Lightbend Inc. 

# Hack to override some of Akka's defaults in Play

# Play's config file loading logic will load this file with a higher
# priority than reference.conf, but a lower priority than application.conf.
# That allows Play to override Akka's reference.conf (which can't happen
# from in Play's own reference.conf), but still allow users to override
# Play's settings in their application.conf.

akka {

  # Play applications should exit when Akka receives a fatal error.
  # If we don't stop the JVM we would have a stale application that
  # can't handle requests since the Akka system is shutdown only.
  jvm-exit-on-fatal-error = on

  # Tell akka to use Slf4jLogger and filter
  loglevel = DEBUG
  loggers = ["akka.event.slf4j.Slf4jLogger"]
  logging-filter = "akka.event.slf4j.Slf4jLoggingFilter"

  # Since Akka 2.5.8 there's a setting to disable all Akka-provided JVM shutdown
  # hooks. Play provides the shutdown hooks and runs the appropriate tasks already.
  # Akka's shutdown hooks are therefore not necessary.
  jvm-shutdown-hooks = off

  # CoordinatedShutdown is an extension introduced in Akka 2.5 that will
  # perform registered tasks in the order that is defined by the phases.
  coordinated-shutdown {

    # Terminate the ActorSystem in the last phase actor-system-terminate.
    terminate-actor-system = on

    # Exit the JVM (System.exit(0)) in the last phase actor-system-terminate.
    # This is disabled by default since it is Play's responsibility
    # to exit the JVM.
    exit-jvm = off

  }
}




© 2015 - 2024 Weber Informatics LLC | Privacy Policy