7132fcd7ac
Today when starting Elasticsearch without a Log4j 2 configuration file, we end up throwing an array index out of bounds exception. This is because we are passing no configuration files to Log4j. Instead, we should throw a useful error message to the user. This commit modifies the Log4j configuration setup to throw a user exception if no Log4j configuration files are present in the config directory. Relates #20493 |
||
---|---|---|
.. | ||
src/test | ||
build.gradle |