-
1. Re: root catagory log is created but relevant content is not
chaituu Dec 6, 2005 9:09 AM (in response to chaituu)I AM GETTING THIS WARNING when i start the server
19:41:37,874 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:log4j.xml
log4j:WARN No appenders could be found for logger (org.jboss.mx.loading.Reposito
ryClassLoader).
log4j:WARN Please initialize the log4j system properly. -
2. Re: root catagory log is created but relevant content is not
buntjer Dec 6, 2005 10:46 AM (in response to chaituu)If thaths your complete log4j.xml then I'm not surprised why it doesn't work.
The file is almost empty. Please repost your current config. -
3. Re: root catagory log is created but relevant content is not
chaituu Dec 7, 2005 2:14 AM (in response to chaituu)complete log4j.xml file;rootCategory logs should go to rolling.log it should not go to server.log.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<!-- ===================================================================== -->
<!-- -->
<!-- Log4j Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- $Id: log4j.xml,v 1.26.2.2 2005/03/02 14:52:20 tdiesler Exp $ -->
<!--
| 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 -->
<!-- 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"/>
-->
<!-- The default pattern: Date Priority [Category] Message\n -->
<!-- The full pattern: Date MS Priority [Category] (Thread:NDC) Message\n
-->
<!-- A size based file rolling appender
-->
<!-- A size based file rolling appender talon.prod.313.log -->
<!-- ============================== -->
<!-- Append messages to the console -->
<!-- ============================== -->
<!-- The default pattern: Date Priority [Category] Message\n -->
<!-- ====================== -->
<!-- More Appender examples -->
<!-- ====================== -->
<!-- Buffer events and log them asynchronously
<appender-ref ref="FILE"/>
<appender-ref ref="CONSOLE"/>
<appender-ref ref="SMTP"/>
-->
<!-- EMail events to an administrator
-->
<!-- Syslog events
-->
<!-- Log events to JMS (requires a topic to be created)
-->
<!-- Log events through SNMP
-->
<!-- ================ -->
<!-- Limit categories -->
<!-- ================ -->
<!-- Limit the org.apache category to INFO as its DEBUG is verbose -->
<appender-ref ref="PROD"/>
<!-- Limit the org.jgroups category to WARN as its INFO is verbose -->
<!-- Limit apache axis to INFO as its DEBUG is even more verbose -->
<!-- Limit JBoss categories -->
<!-- Limit the JSR77 categories -->
<!-- Limit JBoss webservice category
-->
<!-- Decrease the priority threshold for the org.jboss.varia category
-->
<!-- Show the evolution of the DataSource pool in the logs [inUse/Available/Max]
-->
<!--
| 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.
-->
<!--
| 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
<appender-ref ref="TRAP_LOG"/>
<appender-ref ref="TRAP_LOG"/>
<appender-ref ref="TRAP_LOG"/>
<appender-ref ref="TRAP_LOG"/>
<appender-ref ref="TRAP_LOG"/>
-->
<!-- ======================= -->
<!-- Setup the Root category -->
<!-- ======================= -->
<appender-ref ref="CONSOLE"/>
<appender-ref ref="FILE"/>
<appender-ref ref="ROLLING_LOG"/>
<!-- Clustering logging -->
<!-- Uncomment the following to redirect the org.jgroups and
org.jboss.ha categories to a cluster.log file.
<appender-ref ref="CLUSTER"/>
<appender-ref ref="CLUSTER"/>
-->
</log4j:configuration> -
4. Re: root catagory log is created but relevant content is not
buntjer Dec 20, 2005 5:31 AM (in response to chaituu)Maybe a bit late, butter better late than never ;)
Your configurationfile is still a mess.
Make sure you have created a (file)appender. Add the reference to this appender to a logger with the name you use in your application. It's as simple as that.