d273419d00
When a node closes, we shutdown logging as the last statement. This statement must be last lest any subsequent attempts to log will blow up by running into security permissions. Yet, in the case of a tribe node this isn't enough. The first internal tribe node to close will shutdown logging, and subsequent node closes will blow up with the aforementioned problem. This commit migrate the Log4j shutdown to occur as part of the shutdown hook that closes the node, after all nodes have closed. Consequently, we can remove a hack in the test infrastructure to prevent Log4j shutdowns when internal test nodes close and instead just register a single shutdown hook that runs when the test JVM exits. Relates #21519 |
||
|---|---|---|
| .. | ||
| fixtures | ||
| framework | ||
| logger-usage | ||
| build.gradle | ||