logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 36800] New: - LocationInfo not valid for TRACE level calls using new Logger methods
Date Sat, 24 Sep 2005 17:55:27 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36800>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36800

           Summary: LocationInfo not valid for TRACE level calls using new
                    Logger methods
           Product: Log4j
           Version: 1.2
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Layout
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: andy.mcbride@dsl.pipex.com


Caller location info is not being extracted correctly for calls using the new 
trace level methods provided by Logger.  

Using %C, %M etc in a PatternLayout results in '?' being printed instead of the 
proper values.  

The cause is the incorrect classname assigned to the FQCN property in 
Logger.java

The problem does not exist in the 1.3 codebase.

Tested using log4j 1.2.12 on Windows XP with jdk1.5

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

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


Mime
View raw message