* Don't force the logger in the Netty4Plugin class already, at this point log4j might not be fully initialized. * The call was redundant anyway since we do the same thing in the Netty4Transport and Netty4HttpServerTransport classes already and there we do it properly after setting up log4j by initilizing the loggers * Relates #42532
This commit is contained in:
parent
67326252d8
commit
47d50c6774
|
@ -35,7 +35,6 @@ import org.elasticsearch.plugins.NetworkPlugin;
|
|||
import org.elasticsearch.plugins.Plugin;
|
||||
import org.elasticsearch.threadpool.ThreadPool;
|
||||
import org.elasticsearch.transport.netty4.Netty4Transport;
|
||||
import org.elasticsearch.transport.netty4.Netty4Utils;
|
||||
|
||||
import java.util.Arrays;
|
||||
import java.util.Collections;
|
||||
|
@ -45,10 +44,6 @@ import java.util.function.Supplier;
|
|||
|
||||
public class Netty4Plugin extends Plugin implements NetworkPlugin {
|
||||
|
||||
static {
|
||||
Netty4Utils.setup();
|
||||
}
|
||||
|
||||
public static final String NETTY_TRANSPORT_NAME = "netty4";
|
||||
public static final String NETTY_HTTP_TRANSPORT_NAME = "netty4";
|
||||
|
||||
|
|
Loading…
Reference in New Issue