Uploaded image for project: 'logback'
  1. logback
  2. LOGBACK-1520

threadname not correctly resolved in SocketAppender

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.3.0-alpha4
    • Fix Version/s: None
    • Component/s: logback-classic
    • Labels:
      None
    • Environment:

      Windows 10 Pro

      Description

      When using SocketAppender as the only appender for a certain Logger the threadName from the logging event is not evaluated in the calling thread as expected but in the writing thread which does the serialization. This leads to a wrong threadName on consumer side.

      If there are other appenders attached to a certain logger, the threadName is resolved and cached in the LoggingEvent in the calling thread and so it is correct.

        Attachments

          Activity

            People

            Assignee:
            logback-dev Logback dev list
            Reporter:
            wdeifel Wolfgang Deifel
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: