[jira] [Created] (LOG4J2-2689) Inaccuracy in the 'Additivity' section of the 'Configuration' web page

Adrien Guerard created LOG4J2-2689: -- Summary: Inaccuracy in the 'Additivity' section of the 'Configuration' web page Key: LOG4J2-2689 URL: https://issues.apache.org/jira/browse/LOG4J2-2689 Project: L

[jira] [Resolved] (LOGCXX-506) CachedDateFormat reuses timestamps without updating milliseconds after formatting timestamp with ms == 654

[ https://issues.apache.org/jira/browse/LOGCXX-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thorsten Schöning resolved LOGCXX-506. -- Resolution: Fixed Applied again and tests still succeed for me as well. Thanks. > Cach

[GitHub] [logging-log4j2] qxo commented on issue #300: call #StatusLogger.getLogger() only when it's needed.

qxo commented on issue #300: call #StatusLogger.getLogger() only when it's needed. URL: https://github.com/apache/logging-log4j2/pull/300#issuecomment-528440458 > This change looks fine to me. Are there any specific startup scenarios you came across that warrants this? > > Edit: I s

[jira] [Reopened] (LOGCXX-506) CachedDateFormat reuses timestamps without updating milliseconds after formatting timestamp with ms == 654

[ https://issues.apache.org/jira/browse/LOGCXX-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klemens Schölhorn reopened LOGCXX-506: -- I just wanted to move this patch into production and noticed that I only fixed the special

[jira] [Updated] (LOGCXX-506) CachedDateFormat reuses timestamps without updating milliseconds after formatting timestamp with ms == 654

[ https://issues.apache.org/jira/browse/LOGCXX-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Klemens Schölhorn updated LOGCXX-506: - Attachment: 0003-CachedDateFormat-Correct-fix-for-handling-ts-with-65.patch > CachedDateF