Patrik Nordwall 82db446bb7 Don't loadExtensions at startup if already terminated, #27840 (#28248) ... * 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		2019-11-26 11:44:37 +01:00
..
jmx-client	Allow multiple Cluster JMX MBeans in the same JVM (#22484)	2017-03-14 14:31:58 +01:00
src	Don't loadExtensions at startup if already terminated, #27840 (#28248)	2019-11-26 11:44:37 +01:00