[jboss-osgi-issues] [JBoss JIRA] Updated: (JBOSGI-282) Review DEBUG logging volume

Review DEBUG logging volume --------------------------- Key: JBOSGI-282 URL: https://jira.jboss.org/browse/JBOSGI-282 Project: JBoss OSGi Issue Type: Task Security Level: Public(Everyone can see) Components: Productization Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta10 http://blogs.jboss.org/blog/dimitris/2005/04/01/AC08547736BD16504BEC955AE... Another factor that isDebugEnabled() has been abused is due to the fact that in many cases we (developers) have used DEBUG for high traffic logging, that should really be TRACE. The reason being, we (developers) are usually lazy to enable the TRACE level in log4j.xml while developing, and we prefer to just use debug() instead, that we know it will work by default! "If the user doesn't like this, she can turn if off", while the idea should really be, "I need to enable TRACE while I do development, and save server.log from being filled up with garbage, and the user from getting lost inside my verbose traces". * ERROR - A definite problem * WARN - Likely a problem, but can live with it * INFO - Common notifications, lifecycle stuff * DEBUG - Low volume debug * TRACE - High volume debug