I don't remeber that I have configured log4j console appender twice.  I am using the log4j.xml file in the "D:\jboss-3.0.0\server\default\conf" directory which is the one that comes with JBoss distribution.  I am using that config file for DOMConfigurator.configure() method.  Am I doing something really wrong?  It works fine with WebLogic.  I guess that's not relavent since WebLogic doesn't use log4j.  Then, my question is what would be the best way to do loggin in JBoss 3.0?  I have been using this in previous JBoss version and it worked fine... 
What am I doing wrong?
 
The log4j.xml file that I am using (that comes with JBoss) is below...
 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
 
<!-- ===================================================================== -->
<!--                                                                       -->
<!--  Log4j Configuration                                                  -->
<!--                                                                       -->
<!-- ===================================================================== -->
 
<!-- $Id: log4j.xml,v 1.5.2.2 2002/05/23 05:55:43 starksm 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 -->
  <appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender">
    <param name="File" value="${jboss.server.home.dir}/log/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">
    <param name="File" value="${jboss.server.home.dir}/log/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">
    <param name="Threshold" value="INFO"/>
    <param name="Target" value="System.out"/>
 
    <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">
    <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">
    <param name="Threshold" value="ERROR"/>
    <param name="To" value="[EMAIL PROTECTED]"/>
    <param name="From" value="[EMAIL PROTECTED]"/>
    <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">
    <param name="Facility" value="LOCAL7"/>
    <param name="FacilityPrinting" value="true"/>
    <param name="SyslogHost" value="localhost"/>
  </appender>
  -->
 
  <!-- Log events to JMS (requires a topic to be created)
  <appender name="JMS" class="org.apache.log4j.net.JMSAppender">
    <param name="Threshold" value="ERROR"/>
    <param name="TopicConnectionFactoryBindingName" value="java:/ConnectionFactory"/>
    <param name="TopicBindingName" value="topic/MyErrorsTopic"/>
  </appender>
  -->
 
  <!-- ================ -->
  <!-- Limit categories -->
  <!-- ================ -->
 
  <!-- Limit JBoss categories to INFO
  <category name="org.jboss">
    <priority value="INFO"/>
  </category>
  -->
 
  <!-- Increase the priority threshold for the DefaultDS category
  <category name="DefaultDS">
    <priority value="FATAL"/>
  </category>
  -->
 
  <!-- Decrease the priority threshold for the org.jboss.varia category
  <category name="org.jboss.varia">
    <priority value="DEBUG"/>
  </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.
       If you use replace the log4j 1.2 jar with a 1.1.3 jar you will need to
       change this from XLevel to XPriority.
  <category name="org.jboss.system">
    <priority value="TRACE" class="org.jboss.logging.XLevel"/>
  </category>
  <category name="org.jboss.ejb.plugins">
    <priority value="TRACE" class="org.jboss.logging.XLevel"/>
  </category>
  -->
 
  <!-- ======================= -->
  <!-- Setup the Root category -->
  <!-- ======================= -->
 
  <root>
    <appender-ref ref="CONSOLE"/>
    <appender-ref ref="FILE"/>
  </root>
 
</log4j:configuration>
----- Original Message -----
Sent: Wednesday, June 12, 2002 9:12 PM
Subject: Re: [JBoss-user] Doesn't anyone have this problem?

I have seen that before - I think it occurs when you configure log4j console appenders twice - try removing the console appender from your log4j config.
 
hth
dim
----- Original Message -----
Sent: Thursday, June 13, 2002 10:20 AM
Subject: [JBoss-user] Doesn't anyone have this problem?

I posted this message before...  but nobody is responding...  I can't believe I am the only who are having this issue...
Can any one help me?  Why am I getting that error?
 
........................................
 
I am using log4j for logging in one of my servlets.  It was working as intended until I upgraded to JBoss 3.0.0 with integrated Jetty.  I am seeing following error message on the console output.
 
ERROR: invalid console appender config detected, console stream is looping
 
Does anyone know what's going on?
I am using the the log4j.xml file in the D:\jboss-3.0.0\server\default\conf directory for
    DOMConfigurator.configure(configDir + "/log4j.xml");
method.
 
Can anyone tell me what I am doing wrong?
 
Thanks in advance.
 
================================
Mitchell Kim (kimion.com)
Software Developer
[EMAIL PROTECTED]
http://www.kimion.com

Reply via email to