1 Reply Latest reply on Sep 28, 2009 11:30 AM by peterj

There are too many DEBUG written to the

thomas2008ch Sep 28, 2009 7:47 AM

I have a problem: There are too many DEBUG messages written to the "server.log" file so the hard disc gets full every several days. The DEBUG message looks as follow.


2009-09-25 16:18:54,204 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=Naming
2009-09-25 16:18:54,205 DEBUG [org.jboss.naming.NamingService] Creating jboss:service=Naming
2009-09-25 16:18:54,205 DEBUG [org.jboss.naming.NamingService] Created jboss:service=Naming
2009-09-25 16:18:54,225 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=Naming dependents are: []
2009-09-25 16:18:54,225 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=Naming
2009-09-25 16:18:54,225 DEBUG [org.jboss.system.ServiceController] Ignoring create request for service: jboss:service=Naming
2009-09-25 16:18:54,225 DEBUG [org.jboss.system.ServiceController] Creating service jboss:service=JNDIView
2009-09-25 16:18:54,225 DEBUG [org.jboss.naming.JNDIView] Creating jboss:service=JNDIView
2009-09-25 16:18:54,225 DEBUG [org.jboss.naming.JNDIView] Created jboss:service=JNDIView
2009-09-25 16:18:54,226 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss:service=JNDIView dependents are: []
2009-09-25 16:18:54,226 DEBUG [org.jboss.system.ServiceController] Creating service jboss.security:service=SecurityConfig
2009-09-25 16:18:54,226 DEBUG [org.jboss.security.plugins.SecurityConfig] Creating jboss.security:service=SecurityConfig
2009-09-25 16:18:54,226 DEBUG [org.jboss.security.plugins.SecurityConfig] Created jboss.security:service=SecurityConfig
2009-09-25 16:18:54,226 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.security:service=SecurityConfig dependents are: []
2009-09-25 16:18:54,226 DEBUG [org.jboss.system.ServiceController] Creating service jboss.security:service=XMLLoginConfig
2009-09-25 16:18:54,226 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Creating jboss.security:service=XMLLoginConfig
2009-09-25 16:18:54,226 DEBUG [org.jboss.security.auth.login.XMLLoginConfig] Created jboss.security:service=XMLLoginConfig
2009-09-25 16:18:54,227 DEBUG [org.jboss.system.ServiceController] Creating dependent components for: jboss.security:service=XMLLoginConfig dependents are: []
2009-09-25 16:18:54,227 DEBUG [org.jboss.system.ServiceController] Creating service jboss.security:service=JaasSecurityManager
2009-09-25 16:18:54,227 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] Creating jboss.security:service=JaasSecurityManager

I've set the option everywhere in jboss-log4j.xml to INFO but it doesn't help. Can someone help?

Here is my "jboss-log4j.xml":

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">

<!-- ===================================================================== -->
<!-- -->
<!-- Log4j Configuration -->
<!-- -->
<!-- ===================================================================== -->

<!-- $Id: jboss-log4j.xml 75507 2008-07-08 20:15:07Z stan.silvert@jboss.com $ -->

<!--
 | For more configuration infromation and examples see the Jakarta Log4j
 | owebsite: http://jakarta.apache.org/log4j
 -->

<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">

 <!-- ================================= -->
 <!-- Preserve messages in a local file -->
 <!-- ================================= -->

 <!-- A time/date based rolling appender -->
 <appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
 <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
 <param name="File" value="${jboss.server.log.dir}/server.log"/>
 <param name="Append" value="false"/>

 <!-- Rollover at midnight each day -->
 <param name="DatePattern" value="'.'yyyy-MM-dd"/>

 <!-- Rollover at the top of each hour
 <param name="DatePattern" value="'.'yyyy-MM-dd-HH"/>
 -->

 <layout class="org.apache.log4j.PatternLayout">
 <!-- The default pattern: Date Priority [Category] Message\n -->
 <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>

 <!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
 <param name="ConversionPattern" value="%d %-5r %-5p [%c] (%t:%x) %m%n"/>
 -->
 </layout>
 </appender>

 <!-- A size based file rolling appender
 <appender name="FILE" class="org.jboss.logging.appender.RollingFileAppender">
 <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
 <param name="File" value="${jboss.server.log.dir}/server.log"/>
 <param name="Append" value="false"/>
 <param name="MaxFileSize" value="500KB"/>
 <param name="MaxBackupIndex" value="1"/>

 <layout class="org.apache.log4j.PatternLayout">
 <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
 </layout>
 </appender>
 -->

 <!-- ============================== -->
 <!-- Append messages to the console -->
 <!-- ============================== -->

 <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
 <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
 <param name="Target" value="System.out"/>
 <param name="Threshold" value="INFO"/>

 <layout class="org.apache.log4j.PatternLayout">
 <!-- The default pattern: Date Priority [Category] Message\n -->
 <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
 </layout>
 </appender>

 <!-- ====================== -->
 <!-- More Appender examples -->
 <!-- ====================== -->

 <!-- Buffer events and log them asynchronously
 <appender name="ASYNC" class="org.apache.log4j.AsyncAppender">
 <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
 <appender-ref ref="FILE"/>
 <appender-ref ref="CONSOLE"/>
 <appender-ref ref="SMTP"/>
 </appender>
 -->

 <!-- EMail events to an administrator
 <appender name="SMTP" class="org.apache.log4j.net.SMTPAppender">
 <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
 <param name="Threshold" value="ERROR"/>
 <param name="To" value="admin@myhost.domain.com"/>
 <param name="From" value="nobody@myhost.domain.com"/>
 <param name="Subject" value="JBoss Sever Errors"/>
 <param name="SMTPHost" value="localhost"/>
 <param name="BufferSize" value="10"/>
 <layout class="org.apache.log4j.PatternLayout">
 <param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}] %m%n"/>
 </layout>
 </appender>
 -->

 <!-- Syslog events
 <appender name="SYSLOG" class="org.apache.log4j.net.SyslogAppender">
 <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
 <param name="Facility" value="LOCAL7"/>
 <param name="FacilityPrinting" value="true"/>
 <param name="SyslogHost" value="localhost"/>
 <layout class="org.apache.log4j.PatternLayout">
 <param name="ConversionPattern" value="[%d{ABSOLUTE},%c{1}] %m%n"/>
 </layout>
 </appender>
 -->

 <!-- Log events to JMS (requires a topic to be created)
 <appender name="JMS" class="org.apache.log4j.net.JMSAppender">
 <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
 <param name="Threshold" value="ERROR"/>
 <param name="TopicConnectionFactoryBindingName" value="java:/ConnectionFactory"/>
 <param name="TopicBindingName" value="topic/MyErrorsTopic"/>
 </appender>
 -->

 <!-- Log events through SNMP
 <appender name="TRAP_LOG" class="org.apache.log4j.ext.SNMPTrapAppender">
 <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
 <param name="ImplementationClassName" value="org.apache.log4j.ext.JoeSNMPTrapSender"/>
 <param name="ManagementHost" value="127.0.0.1"/>
 <param name="ManagementHostTrapListenPort" value="162"/>
 <param name="EnterpriseOID" value="1.3.6.1.4.1.24.0"/>
 <param name="LocalIPAddress" value="127.0.0.1"/>
 <param name="LocalTrapSendPort" value="161"/>
 <param name="GenericTrapType" value="6"/>
 <param name="SpecificTrapType" value="12345678"/>
 <param name="CommunityString" value="public"/>
 <param name="ForwardStackTraceWithTrap" value="true"/>
 <param name="Threshold" value="INFO"/>
 <param name="ApplicationTrapOID" value="1.3.6.1.4.1.24.12.10.22.64"/>
 <layout class="org.apache.log4j.PatternLayout">
 <param name="ConversionPattern" value="%d,%p,[%t],[%c],%m%n"/>
 </layout>
 </appender>
 -->

 <!-- Emit events as JMX notifications
 <appender name="JMX" class="org.jboss.monitor.services.JMXNotificationAppender">
 <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>

 <param name="Threshold" value="WARN"/>
 <param name="ObjectName" value="jboss.system:service=Logging,type=JMXNotificationAppender"/>

 <layout class="org.apache.log4j.PatternLayout">
 <param name="ConversionPattern" value="%d %-5p [%c] %m"/>
 </layout>
 </appender>
 -->

 <!-- ================ -->
 <!-- Limit categories -->
 <!-- ================ -->

 <!-- Limit the org.apache category to INFO as its DEBUG is verbose -->
 <category name="org.apache">
 <priority value="INFO"/>
 </category>

 <!-- Limit the jacorb category to WARN as its INFO is verbose -->
 <category name="jacorb">
 <priority value="WARN"/>
 </category>

 <!-- Limit the org.jgroups category to WARN as its INFO is verbose -->
 <category name="org.jgroups">
 <priority value="WARN"/>
 </category>

 <!-- Limit the org.quartz category to INFO as its DEBUG is verbose -->
 <category name="org.quartz">
 <priority value="INFO"/>
 </category>

 <!-- Limit JSF logging to DEBUG. FINER and FINEST will not be logged -->
 <category name="javax.enterprise.resource.webcontainer.jsf">
 <priority value="INFO" />
 </category>

 <!-- Limit JBoss categories
 <category name="org.jboss">
 <priority value="INFO"/>
 </category>
 -->

 <!-- Limit the JSR77 categories -->
 <category name="org.jboss.management">
 <priority value="INFO"/>
 </category>

 <!-- Show the evolution of the DataSource pool in the logs [inUse/Available/Max]
 <category name="org.jboss.resource.connectionmanager.JBossManagedConnectionPool">
 <priority value="TRACE"/>
 </category>
 -->

 <!-- Limit the org.jboss.serial (jboss-serialization) to INFO as its DEBUG is verbose -->
 <category name="org.jboss.serial">
 <priority value="INFO"/>
 </category>

 <!-- Decrease the priority threshold for the org.jboss.varia category
 <category name="org.jboss.varia">
 <priority value="INFO"/>
 </category>
 -->

 <!-- Enable JBossWS message tracing
 <category name="org.jboss.ws.core.MessageTrace">
 <priority value="TRACE"/>
 </category>
 -->

 <!--
 | An example of enabling the custom TRACE level priority that is used
 | by the JBoss internals to diagnose low level details. This example
 | turns on TRACE level msgs for the org.jboss.ejb.plugins package and its
 | subpackages. This will produce A LOT of logging output.
 |
 | Note: since jboss AS 4.2.x, the trace level is supported natively by
 | log4j, so although the custom org.jboss.logging.XLevel priority will
 | still work, there is no need to use it. The two examples that follow
 | will both enable trace logging.
 <category name="org.jboss.system">
 <priority value="TRACE" class="org.jboss.logging.XLevel"/>
 </category>
 <category name="org.jboss.ejb.plugins">
 <priority value="TRACE"/>
 </category>
 -->

 <!--
 | Logs these events to SNMP:
 - server starts/stops
 - cluster evolution (node death/startup)
 - When an EJB archive is deployed (and associated verified messages)
 - When an EAR archive is deployed

 <category name="org.jboss.system.server.Server">
 <priority value="INFO" />
 <appender-ref ref="TRAP_LOG"/>
 </category>

 <category name="org.jboss.ha.framework.interfaces.HAPartition.lifecycle">
 <priority value="INFO" />
 <appender-ref ref="TRAP_LOG"/>
 </category>

 <category name="org.jboss.deployment.MainDeployer">
 <priority value="ERROR" />
 <appender-ref ref="TRAP_LOG"/>
 </category>

 <category name="org.jboss.ejb.EJBDeployer">
 <priority value="INFO" />
 <appender-ref ref="TRAP_LOG"/>
 </category>

 <category name="org.jboss.deployment.EARDeployer">
 <priority value="INFO" />
 <appender-ref ref="TRAP_LOG"/>
 </category>
 -->

 <!-- Clustering logging -->
 <!-- Uncomment the following to redirect the org.jgroups and
 org.jboss.ha categories to a cluster.log file.

 <appender name="CLUSTER" class="org.jboss.logging.appender.RollingFileAppender">
 <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
 <param name="File" value="${jboss.server.log.dir}/cluster.log"/>
 <param name="Append" value="false"/>
 <param name="MaxFileSize" value="500KB"/>
 <param name="MaxBackupIndex" value="1"/>

 <layout class="org.apache.log4j.PatternLayout">
 <param name="ConversionPattern" value="%d %-5p [%c] %m%n"/>
 </layout>
 </appender>
 <category name="org.jgroups">
 <priority value="INFO" />
 <appender-ref ref="CLUSTER"/>
 </category>
 <category name="org.jboss.ha">
 <priority value="INFO" />
 <appender-ref ref="CLUSTER"/>
 </category>
 -->

 <!-- ======================= -->
 <!-- Setup the Root category -->
 <!-- ======================= -->

 <root>
 <appender-ref ref="CONSOLE"/>
 <appender-ref ref="FILE"/>
 </root>

</log4j:configuration>

1. Re: There are too many DEBUG written to the

peterj Sep 28, 2009 11:30 AM (in response to thomas2008ch)
Do you want to turn off all debugging? If so, then there are two possibilities. You only need to do one of them, not both.

1) Add a threshold to the FILE appender:

<appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender"> . . . <param name="Threshold" value="${jboss.server.log.threshold}"/> . . .

2) Add a priority to the root:

<root> <priority value="INFO"/> <appender-ref ref="CONSOLE"/> <appender-ref ref="FILE"/> </root>

By the way, the FILE appender uses a rolling daily appender so each day you should get a new log file - why not simply have a cron script that runs every day and deletes all log files more than X days old?
Actions