Uploaded image for project: 'SLF4J'
  1. SLF4J
  2. SLF4J-63

Performance and the JDK1.4 logger

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Implementations
    • Labels:
      None
    • Environment:

      Operating System: Windows XP
      Platform: All

      Description

      Accoding to Ian Carr, the fillCallerData method is called even for disabled log statements.

      private void log(String callerFQCN, Level level, String msg, Throwable t)

      { // millis and thread are filled by the constructor LogRecord record = new LogRecord(level, msg); record.setLoggerName(getName()); record.setThrown(t); fillCallerData(callerFQCN, record); <-- bad logger.log(record); }

      For more information see http://www.slf4j.org/pipermail/user/2008-February/000486.html

        Attachments

          Activity

            People

            • Assignee:
              slf4j-dev SLF4J developers list
              Reporter:
              listid@qos.ch Ceki Gulcu
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: