82db446bb7
* Problem could be recreated with DowningProviderSpec when running with -Dakka.remote.artery.enabled=off * The exception from the downing provider caused cluster shutdown followed by CoordinatedShutdown and ActorSystem.finalTerminate * The ActorSystem had still not fully initialized so it tried to load the configured extensions and the SystemMaterializer extension * SystemMaterializer can't create child actor * The thrown exception isn't wrong but might be confusing * Skip loading extensions if ActorSystem already terminated * The reason for different behavior with Artery and classic remoting is that Artery inits the SystemMaterializer earlier |
||
|---|---|---|
| .. | ||
| main | ||
| multi-jvm/scala/akka/cluster | ||
| test | ||