[
https://issues.apache.org/jira/browse/LOG4J2-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287850#comment-16287850
]
Ralph Goers commented on LOG4J2-2055:
-
Since this issue is closed I would suggest you open a
Gary Gregory created LOG4J2-2149:
Summary: Update Jackson from 2.9.2 to 2.9.3
Key: LOG4J2-2149
URL: https://issues.apache.org/jira/browse/LOG4J2-2149
Project: Log4j 2
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LOG4J2-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287744#comment-16287744
]
Ralph Goers commented on LOG4J2-2055:
-
This stack trace is a little different in that it involves
[
https://issues.apache.org/jira/browse/LOG4J2-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287630#comment-16287630
]
Gary Gregory commented on LOG4J2-2148:
--
I would start by using the current version: 2.10.0.
>
[
https://issues.apache.org/jira/browse/LOG4J2-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petr Valenta updated LOG4J2-2148:
-
Description:
Hi.
I tried CronTriggeringPolicy(version 2.8) for save daily log files at midnight.
Petr Valenta created LOG4J2-2148:
Summary: CronTriggeringPolicy renaming behavior
Key: LOG4J2-2148
URL: https://issues.apache.org/jira/browse/LOG4J2-2148
Project: Log4j 2
Issue Type:
Tobias Bindel created LOG4NET-585:
-
Summary: log4net became very slow with caller location information
after Windows 10 Fall Creators Update (1709)
Key: LOG4NET-585
URL:
