You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2009/02/06 22:52:42 UTC

DO NOT REPLY [Bug 46668] New: Level.ALL does not include Level.TRACE

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

           Summary: Level.ALL does not include Level.TRACE
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Windows Server 2003
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Appender
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: asf-bugzilla@rodneybeede.com


When I setup an appender to have a threshold of Level.ALL any log.trace() calls
do not get logged.

Should Level.ALL include that level as well.  If not then the api doc should be
updated to indicate so.


-- 
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


DO NOT REPLY [Bug 46668] Level.ALL does not include Level.TRACE

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46668





--- Comment #3 from Curt Arnold <ca...@apache.org>  2009-02-19 04:25:48 PST ---
The reporter wasn't setting the level of a logger, he was setting the threshold
of an appender.  Since the trace event never satisfied the effective level of
the logger (likely debug by default), it never would have made it to an
appender for the threshold to have any effect.  Since setting the threshold did
not have the affect he expected, he assumed the defect was in the Level class.

As long as he set any Logger to Level.ALL or Level.TRACE he would have been ok,
he just chose the root.  There was no need to touch the threshold of the
Appender.


-- 
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


DO NOT REPLY [Bug 46668] Level.ALL does not include Level.TRACE

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46668


Rodney <as...@rodneybeede.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #1 from Rodney <as...@rodneybeede.com>  2009-02-06 14:04:37 PST ---
Logger.getRootLogger().setLevel(Level.ALL);

That fixed the issue.  Setting an individual appender to trace doesn't work
unless the root logger has that set first.

Perhaps some note in the api doc would be useful.


-- 
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


DO NOT REPLY [Bug 46668] Level.ALL does not include Level.TRACE

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=46668





--- Comment #2 from Jacob Kjome <ho...@visi.com>  2009-02-18 22:35:05 PST ---
Not sure why you resolved this as invalid?  Setting Level.ALL to any individual
logger in order to get trace() calls displaying for that logger should work
without any manipulation of the root logger.  If it doesn't, then there is a
bug, IMO.  I haven't attempted to verify it, but if you attach a testcase
showing the bad behavior, it can certainly be fixed.  I leave it up to you as
to whether to reopen the bug.

Jake


-- 
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