d4947c26ae
We have some packaging tests where we use a custom jvm.options file. The flags we use here are barebones, just enough to exercise that using a custom jvm.options files actually works. Due to this, we are missing a Log4j flag that prevents Log4j from trying to use JMX. If Log4j tries to use JMX, it hits a security manager exception and tries to log this. This attempt to log happens before we've configured logging. Previously, Elasticsearch was lenient here so this was treated as harmless and the test could march on. Now, we fail startup if we detect an attempt to log before logging is configured so this prevents Elasticsearch from starting if we do not have jvm.options files in place that prevent these log messages from being written before logging is being configured. This commit adds jvm.options files in the places need to prevent this. |
||
|---|---|---|
| .. | ||
| backwards-5.0 | ||
| evil-tests | ||
| multi-cluster-search | ||
| no-bootstrap-tests | ||
| rolling-upgrade | ||
| smoke-test-client | ||
| smoke-test-http | ||
| smoke-test-ingest-disabled | ||
| smoke-test-ingest-with-all-dependencies | ||
| smoke-test-multinode | ||
| smoke-test-plugins | ||
| smoke-test-reindex-with-painless | ||
| smoke-test-tribe-node | ||
| vagrant | ||