LOG Level, not working

[gabrielq...@gmail.com]

I'm trying to set the log level of the eureka-server-war, I already tried with the log4j properties file but it didn't work. Also I added this property log4j.appender.stdout.File=${CATALINA_HOME}/logs/catalina.out but same result. The application still send DEBUG level of logs, when i have everything seted in ERROR.

[Tomasz Bak]

The default log level in eureka.war is set to INFO, and this is what I am getting when running it in tomcat.

Can you tell me which version of eureka you are running, and which servlet container?

On Thu, Oct 8, 2015 at 10:22 AM, <gabrielq...@gmail.com> wrote:

I'm trying to set the log level of the eureka-server-war, I already tried with the log4j properties file but it didn't work. Also I added this property log4j.appender.stdout.File=${CATALINA_HOME}/logs/catalina.out but same result. The application still send DEBUG level of logs, when i have everything seted in ERROR.

--
You received this message because you are subscribed to the Google Groups "eureka_netflix" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eureka_netfli...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gabrielq...@gmail.com]

eureka-client-1.1.150 that's the client version that is causing the problems and tomcat 7.

[Tomasz Bak]

That is very old version. Could you upgrade to the latest release (1.2.5), and verify it the problem is still there?

[gabrielq...@gmail.com]

Getting the same error. Even when i set the log level to ERROR i got this:



20:25:38,416 DEBUG [headers] << HTTP/1.1 200 OK
20:25:38,416 DEBUG [headers] << Server: Apache-Coyote/1.1
20:25:38,416 DEBUG [headers] << Content-Encoding: gzip
20:25:38,417 DEBUG [headers] << Vary: Accept-Encoding
20:25:38,417 DEBUG [headers] << Content-Type: application/json
20:25:38,417 DEBUG [headers] << Content-Length: 543
20:25:38,417 DEBUG [headers] << Date: Thu, 08 Oct 2015 20:25:38 GMT
20:25:38,417 DEBUG [DefaultHttpClient] Connection can be kept alive indefinitely

[Tomasz Bak]

I have just run eureka-server:1.2.5 on a fresh tomcat7 installation, and I am not getting any DEBUG logs. You must have something in your environment. Can you make a new, isolated deployment?

[Gabriel Quijada]

In an isolated deployment will not happen, the discovery client is sending hearthnreaths and causing those logs. It just happena in those moments with the http request

You received this message because you are subscribed to a topic in the Google Groups "eureka_netflix" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/eureka_netflix/UsqC3mldZUU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to eureka_netfli...@googlegroups.com.

[Tomasz Bak]

So this is apache http client logging, which is using commons-logging. Maybe it is not being bridge to log4j for some reason?

[Gabriel Quijada]

Log4j file is considered, even it appears as succesfully read on catalina.out with error log, but there is some portion of code that is not using that.