[JIRA] Created: (LBCLASSIC-122) %contextName with HTMLLayout produces empty logfiles

%contextName with HTMLLayout produces empty logfiles ---------------------------------------------------- Key: LBCLASSIC-122 URL: http://jira.qos.ch/browse/LBCLASSIC-122 Project: logback-classic Issue Type: Bug Components: layout Affects Versions: 0.9.15 Reporter: Rick Janda Assignee: Logback dev list Hello Logback team, I encountered a unexpected behavior when trying to print out the log context name in the html output. I configured a FileAppender with the following layout: <layout class="ch.qos.logback.classic.html.HTMLLayout"> <Pattern>%d{HH:mm:ss.SSS}%mdc{refId}%contextName%msg</Pattern> </layout> With this pattern, non of the log messages end up in the file. The output completely stops after the table header. If I remove "%contextName" from the pattern, I get my log messages written to the file as expected. Could you please have a look at this issue. Thank you in advance for your help. Kind regards, Rick -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.qos.ch/browse/LBCLASSIC-122?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-122: -------------------------------------- Hello Rick, Thank you for this report. What is your context name? In particular, does the context name contain special characters such as '<' or '>' ?
%contextName with HTMLLayout produces empty logfiles ----------------------------------------------------
Key: LBCLASSIC-122 URL: http://jira.qos.ch/browse/LBCLASSIC-122 Project: logback-classic Issue Type: Bug Components: layout Affects Versions: 0.9.15 Reporter: Rick Janda Assignee: Logback dev list
Hello Logback team, I encountered a unexpected behavior when trying to print out the log context name in the html output. I configured a FileAppender with the following layout: <layout class="ch.qos.logback.classic.html.HTMLLayout"> <Pattern>%d{HH:mm:ss.SSS}%mdc{refId}%contextName%msg</Pattern> </layout> With this pattern, non of the log messages end up in the file. The output completely stops after the table header. If I remove "%contextName" from the pattern, I get my log messages written to the file as expected. Could you please have a look at this issue. Thank you in advance for your help. Kind regards, Rick
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.qos.ch/browse/LBCLASSIC-122?page=com.atlassian.jira.plugin.syste... ] Rick Janda commented on LBCLASSIC-122: -------------------------------------- Hello Ceki, the context name is "baa-hnm_test2" (without the quotes). Regards, Rick
%contextName with HTMLLayout produces empty logfiles ----------------------------------------------------
Key: LBCLASSIC-122 URL: http://jira.qos.ch/browse/LBCLASSIC-122 Project: logback-classic Issue Type: Bug Components: layout Affects Versions: 0.9.15 Reporter: Rick Janda Assignee: Logback dev list
Hello Logback team, I encountered a unexpected behavior when trying to print out the log context name in the html output. I configured a FileAppender with the following layout: <layout class="ch.qos.logback.classic.html.HTMLLayout"> <Pattern>%d{HH:mm:ss.SSS}%mdc{refId}%contextName%msg</Pattern> </layout> With this pattern, non of the log messages end up in the file. The output completely stops after the table header. If I remove "%contextName" from the pattern, I get my log messages written to the file as expected. Could you please have a look at this issue. Thank you in advance for your help. Kind regards, Rick
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
participants (2)
-
Ceki Gulcu (JIRA)
-
Rick Janda (JIRA)