Too Many Logs

Please answer these questions before submitting your issue.

What version of gRPC are you using?

1.0.0

What JVM are you using (java -version)?

1.8

What did you do?

If possible, provide a recipe for reproducing the error. Not sure.

What did you expect to see?

No logs.

What did you see instead.

[id: 0xbf3948c7, L:/127.0.0.1:56373 - R:localhost/127.0.0.1:8080] DATA: streamId=5, padding=0, endStream=false, length=166, bytes=00000000a10a02696412640000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000...

------------------------------------
11:36:20.377 [grpc-default-worker-ELG-2-13] DEBUG io.grpc.netty.NettyClientHandler - 
----------------INBOUND--------------------

[id: 0xbf3948c7, L:/127.0.0.1:56373 - R:localhost/127.0.0.1:8080] DATA: streamId=5, padding=0, endStream=false, length=166, bytes=00000000a10a02696412640000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000...
11:36:20.377 [grpc-default-worker-ELG-2-13] DEBUG io.grpc.netty.NettyClientHandler - 
------------------------------------

I am pretty new to using grpc-java so this might be a very basic issue. When I run my code I receive extensive logging (seen above). So much so that it has crashed my IDE before. I have tried to follow the thread here:

https://github.com/grpc/grpc-java/issues/1577

Logger log = Logger.getlogger(“io.grpc”); log.setLevel(Level.WARNING);

Unfortunately, I have had no success. Has anyone else seen this issue or know of a solution?

[adam-26]

This happens because netty uses SLF4J and it will bind to a logging framework if it exists in your class path.

Removing the log output is a 2 step process.

1. Determine the logging framework SLF4J is bound to
2. Configure the bound logging framework so that it doesn’t write debug output

An example of doing this can be found on StackOverflow (the code below is copied from the StackOverflow post).

import org.slf4j.impl.StaticLoggerBinder;

// 1. Determine what logging framework SLF4J is bound to:
final StaticLoggerBinder binder = StaticLoggerBinder.getSingleton();

// this will print the name of the logger factory to stdout
System.out.println(binder.getLoggerFactoryClassStr());

[thomasjungblut]

I worked around it by forcing log4j as the logging backend and setting io.netty to INFO.

static {
        InternalLoggerFactory.setDefaultFactory(Log4JLoggerFactory.INSTANCE);
        LoggerContext ctx = (LoggerContext) LogManager.getContext(false);
        Configuration config = ctx.getConfiguration();
        LoggerConfig loggerConfig = config.getLoggerConfig("io.netty");
        loggerConfig.setLevel(Level.INFO);
        ctx.updateLoggers();
    }