[jira] [Assigned] (LOG4J2-2064) Publish new log4j-server on maven central repository

[ https://issues.apache.org/jira/browse/LOG4J2-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-2064: --- Assignee: Ralph Goers > Publish new log4j-server on maven central repository > -

[jira] [Closed] (LOG4J2-1768) MDC.clear() is broken in Log4j-1_2-api = 2.4

[ https://issues.apache.org/jira/browse/LOG4J2-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-1768. --- Resolution: Incomplete Closing due to lack of response from reporter. > MDC.clear() is broken in Log

[jira] [Assigned] (LOG4J2-2061) RollingFileManager not removed when RollingFileAppender is stopped, using DirectWriteRolloverStrategy

[ https://issues.apache.org/jira/browse/LOG4J2-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers reassigned LOG4J2-2061: --- Assignee: Ralph Goers > RollingFileManager not removed when RollingFileAppender is stopped,

[jira] [Commented] (LOG4J2-2120) Json escaping does not properly escape newlines

[ https://issues.apache.org/jira/browse/LOG4J2-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254347#comment-16254347 ] ASF GitHub Bot commented on LOG4J2-2120: GitHub user cakofony opened a pull reque

[GitHub] logging-log4j2 pull request #133: LOG4J2-2120: Json escaping handles newline...

GitHub user cakofony opened a pull request: https://github.com/apache/logging-log4j2/pull/133 LOG4J2-2120: Json escaping handles newline correctly You can merge this pull request into a Git repository by running: $ git pull https://github.com/cakofony/logging-log4j2 LOG4J2-212

[jira] [Created] (LOG4J2-2120) Json escaping does not properly escape newlines

Carter Douglas Kozak created LOG4J2-2120: Summary: Json escaping does not properly escape newlines Key: LOG4J2-2120 URL: https://issues.apache.org/jira/browse/LOG4J2-2120 Project: Log4j 2

Jenkins build became unstable: Log4j 2.x #3179

See

[GitHub] logging-log4j2 pull request #132: ParameterFormatter.deepToString checks mor...

Github user asfgit closed the pull request at: https://github.com/apache/logging-log4j2/pull/132 ---

[jira] [Commented] (LOG4J2-2118) MutableLogEvent does not retain the Message format string

[ https://issues.apache.org/jira/browse/LOG4J2-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254149#comment-16254149 ] Mikael Ståldal commented on LOG4J2-2118: Maybe a _read optimized format_ like Ion

[GitHub] logging-log4j2 issue #130: How can I use CachedClock

Github user mikaelstaldal commented on the issue: https://github.com/apache/logging-log4j2/pull/130 GitHub Pull Requests is not an appropriate way to ask questions. Try the [`log4j-user`](https://logging.apache.org/log4j/2.x/mail-lists.html) mailing list. ---

[GitHub] logging-log4j2 issue #132: ParameterFormatter.deepToString checks more speci...

Github user cakofony commented on the issue: https://github.com/apache/logging-log4j2/pull/132 Added byte (to the StringBuilders helper as well). I avoided BigDecimal/BigInteger because they're non-final, it's possible they may be implemented to support StringBuilderFormattabl

[GitHub] logging-log4j2 pull request #132: ParameterFormatter.deepToString checks mor...

GitHub user cakofony opened a pull request: https://github.com/apache/logging-log4j2/pull/132 ParameterFormatter.deepToString checks more special types This change allows us to avoid StringBuilder usage for primitives. You can merge this pull request into a Git repository by running

[jira] [Commented] (LOG4J2-1883) Timestamp does not seem to support microseconds level

[ https://issues.apache.org/jira/browse/LOG4J2-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253763#comment-16253763 ] Remko Popma commented on LOG4J2-1883: - I’ll try to make progress on this soon, starti

[jira] [Commented] (LOG4NET-573) Appenders Deadlock

[ https://issues.apache.org/jira/browse/LOG4NET-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253747#comment-16253747 ] Paul Mendoza commented on LOG4NET-573: -- I figured out the problem. On Windows 10 if

[jira] [Updated] (LOG4NET-573) Appenders Deadlock

[ https://issues.apache.org/jira/browse/LOG4NET-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Mendoza updated LOG4NET-573: - Attachment: screenshot-2.png > Appenders Deadlock > -- > > Key: L

[jira] [Updated] (LOG4NET-573) Appenders Deadlock

[ https://issues.apache.org/jira/browse/LOG4NET-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Mendoza updated LOG4NET-573: - Attachment: screenshot-1.png > Appenders Deadlock > -- > > Key: L

[jira] [Resolved] (LOG4J2-2119) log4j-core do not include log4j-api

[ https://issues.apache.org/jira/browse/LOG4J2-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2119. - Resolution: Cannot Reproduce > log4j-core do not include log4j-api >

[jira] [Updated] (LOG4J2-2119) log4j-core do not include log4j-api

[ https://issues.apache.org/jira/browse/LOG4J2-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-2119: Attachment: test.zip The attached zip file was created using mvn archetype:generate to create a st

[jira] [Commented] (LOG4J2-2084) syslog appender stops working after upgrade from 2.8.2 to 2.9.1

[ https://issues.apache.org/jira/browse/LOG4J2-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253462#comment-16253462 ] dennis lucero commented on LOG4J2-2084: --- [~martin.schroeder] Please see issue to co

[jira] [Created] (LOG4J2-2119) log4j-core do not include log4j-api

dennis lucero created LOG4J2-2119: - Summary: log4j-core do not include log4j-api Key: LOG4J2-2119 URL: https://issues.apache.org/jira/browse/LOG4J2-2119 Project: Log4j 2 Issue Type: Bug