gitblit plugin with Tomcat 7 massive debug logs

[Bassem Rabil]

Hi 

We have Gerrit 2.7 deployed with tomcat 7 and gitblit plugin for repositories browsing, in the catalina.out we have massive debug statements coming from gitblit. We tried to set debug=0 in tomcat configuration and set explicitly the property in gitblit "web.debugMode = false" and still these debug statements are added to catalina.out.

Samples from these debug statements are below:

[2013-10-29 12:26:50,824] DEBUG org.apache.wicket.Component : Begin render [MarkupContainer [Component id = link]]

[2013-10-29 12:26:50,824] DEBUG org.apache.wicket.Component : Begin render [Component id = label]

[2013-10-29 12:26:50,824] DEBUG org.apache.wicket.Component : End render [Component id = label]

[2013-10-29 12:26:50,824] DEBUG org.apache.wicket.Component : End render [MarkupContainer [Component id = link]]

[2013-10-29 12:26:50,824] DEBUG org.apache.wicket.MarkupContainer : Rendering raw markup

Did any of you face this issue before ? 

Any hints on how to disable this verbose mode for the gitblit plugin with tomcat is highly appreciated.

Thanks and Regards

Bassem Rabil Guendy

[lucamilanesio]

Hi Bassem,

actually I don't think the problem is on the web.debugMode but rather on the internal Wicket LOG4J debug.

Do you have any log4j.properties in the classpath ?

Possibly the shading during the gitblit-plugin build may have included a log4j with root logger set to DEBUG.

Do a jar tvf of the gitblit plugin and extract the log4j.properties to check this out.

HTH.

Luca.

[Bassem Rabil]

I checked the content of the log4j.properties extracted from gitblit.jar. It seems to me debug is already commented out. Please have a look, I might be missing something there, i.e.

log4j.rootCategory=INFO, S

#log4j.rootLogger=INFO

#log4j.logger.org=INFO

#log4j.logger.com=INFO

#log4j.logger.net=INFO

#log4j.logger.com.gitblit=DEBUG

log4j.logger.org.apache.wicket=INFO

log4j.logger.org.apache.wicket.RequestListenerInterface=WARN

log4j.logger.org.apache.wicket.protocol.http.HttpSessionStore=WARN

Do you think we need to set this property log4j.logger.com.gitblit=WARN instead and uncomment it ?

Thanks and Regards

Bassem Guendy

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
 
---
You received this message because you are subscribed to a topic in the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/repo-discuss/oNLPBL4pGzw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Bruce Zu]

On Tuesday, November 12, 2013 9:19:39 PM UTC+8, Bassem Rabil wrote:

I checked the content of the log4j.properties extracted from gitblit.jar. It seems to me debug is already commented out. Please have a look,

I delete the  log4j.properties from gitblit.jar. redeploy and restart tomcat , the issue is still there jumping.

any update on CATALINA_BASE/conf/logging.properties can get the issue away. 

[Bruce Zu]

Gustaf had an idea to control the DEBUG massive log via tomcat .I carried it out after reading http://hwellmann.blogspot.com/2012/11/logging-with-slf4j-and-logback-in.html. we use tomcat7.0.22 and.  it can work.  share here for reference.

[Bassem Rabil]

Hi Bruce

Were you able to get rid of massive debug logging using this alternative logging library for Tomcat ?

Regards

Bassem

[Bruce Zu]

On Sunday, November 17, 2013 2:34:14 AM UTC+8, Bassem Rabil wrote:

Hi Bruce

Were you able to get rid of massive debug logging using this alternative logging library for Tomcat ?

yes it works. I am using it now.