[logback-dev] [JIRA] Updates for LOGBACK-1540: threadName has empty value that is logged via logback-access
QOS.CH (JIRA)
noreply-jira at qos.ch
Thu Nov 12 14:15:00 CET 2020
logback / LOGBACK-1540 [Open]
threadName has empty value that is logged via logback-access
==============================
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
https://jira.qos.ch/browse/LOGBACK-1540
==============================
Issue created
------------------------------
Krystian created this issue on 12/Nov/20 2:00 PM
Summary: threadName has empty value that is logged via logback-access
Issue Type: Bug
Affects Versions: 1.2.3, 1.3.0-alpha5
Assignee: Logback dev list
Created: 12/Nov/20 2:00 PM
Environment:
Jetty 9.4.34.v20201102
Debian
Priority: Major
Reporter: Krystian
Description:
according to the documentation: https://logback.qos.ch/manual/layouts.html
|[|https://logback.qos.ch/manual/layouts.html#threadName]*I / threadName*|Name of the thread which processed the request.|
but when you set [%*I*] or [%*threadName*] at logback-access.xml
in the log file will be saved "[-]"
no value is set as threadName,
eg.
<encoder>
<pattern>%h %l %u [%date\{ISO8601}] [%I] "%r" %s %b "%i\{Referer}" [%D]ms</pattern>
</encoder>
==============================
This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)
More information about the logback-dev
mailing list