[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-dev
Subject:    DO NOT REPLY [Bug 48209] New: Websphere 6.0: logging statement
From:       bugzilla () apache ! org
Date:       2009-11-17 8:48:51
Message-ID: bug-48209-31091 () https ! issues ! apache ! org/bugzilla/
[Download RAW message or body]

https://issues.apache.org/bugzilla/show_bug.cgi?id=48209

           Summary: Websphere 6.0: logging statement appear in the
                    SYSPRINT (System.out)
           Product: Log4j
           Version: 1.2
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Appender
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: fj.walraven@belastingdienst.nl


Created an attachment (id=24547)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=24547)
WASlog

We have configured log4j for ERRORs to go to the file-appender and FATALs to go
to the console-appender (the ConsoleAppender, or System.out, in the Websphere
environment ultimately writes to a file called SYSPRINT):
---
log4j.threshold=ERROR
log4j.rootLogger=ERROR, ConsoleAppender, SUBAppender
#
# Geen interne logging voor log4j
#
log4j.debug=false

#
# Console Appender
#
log4j.appender.ConsoleAppender=org.apache.log4j.ConsoleAppender
log4j.appender.ConsoleAppender.threshold=FATAL
log4j.appender.ConsoleAppender.immediateFlush=true
log4j.appender.ConsoleAppender.Target=System.out
log4j.appender.ConsoleAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.ConsoleAppender.layout.ConversionPattern=%d{ISO8601} %-4.4d{z}
SUB2009.03.19 %-5p %m %C %M %X{userId} %X{hostname}%n

#
# Default appender voor applicatieve logging
#
log4j.appender.SUBAppender=org.apache.log4j.DailyRollingFileAppender
log4j.appender.SUBAppender.threshold=ERROR
log4j.appender.SUBAppender.DatePattern='.'yyyy-MM-dd
log4j.appender.SUBAppender.immediateFlush=true
log4j.appender.SUBAppender.File=/wasconfig/V6R0/wpe1logs/applogs/SUB/HLPVOA.log
log4j.appender.SUBAppender.BufferedIO=false
log4j.appender.SUBAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.SUBAppender.layout.ConversionPattern=%d{ISO8601} %-4.4d{z}
SUB2009.03.19 %-5p %m %C %M %X{userId} %X{hostname}%n
---

In the production environment we see a couple of remarkable things:
- The logging statements are sent to the SUBAppender (file-appender) without
any problem. The output file is correct.
- ERROR logging statements appear in the SYSPRINT (console-appender) where
there should only be FATALs (see threshold)
- logging into the SYSPRINT starts everyday randomly (the server is restarted
everyday)
- there are days that there is no logging into the SYSPRINT
- If we remove the (ConsoleAppender) reference from the root-logger there is no
change in behaviour: the logging statements still appear in the SYSPRINT
- The logging statements in the SYSPRINT start repeating (from 2 to 1000 times)
- See attachment (WASlog) for the SYSPRINT that contains logging statements
that do not seem to follow the formatting according to the log4j-config file.
The labels PROFILING_LOGGING and OPDRACHT_LOGGING have a level higher than
ERROR but lower than FATAL
- We have contacted IBM and they say it is a log4j problem

Can anybody explain what goes wrong here?

Regards,
Frits Walraven

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]