[logback-dev] [JIRA] Updates for LOGBACK-1520: threadname not correctly resolved in SocketAppender
noreply-jira at qos.ch
Mon Aug 10 14:10:00 CEST 2020
logback / LOGBACK-1520 [Open]
threadname not correctly resolved in SocketAppender
Here's what changed in this issue in the last few minutes.
This issue has been created
This issue is now assigned to you.
View or comment on issue using this link
Wolfgang Deifel created this issue on 10/Aug/20 1:59 PM
Summary: threadname not correctly resolved in SocketAppender
Issue Type: Bug
Affects Versions: 1.3.0-alpha4
Assignee: Logback dev list
Created: 10/Aug/20 1:59 PM
Environment: Windows 10 Pro
Reporter: Wolfgang Deifel
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.
This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)
More information about the logback-dev