[jira] [Commented] (LOG4J2-2536) -> value is output as is

[ https://issues.apache.org/jira/browse/LOG4J2-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453823#comment-17453823 ] Volkan Yazici commented on LOG4J2-2536: --- [~rgoers], shall we share this as a recom

[jira] [Updated] (LOGCXX-536) CMakeLists.txt install pgkconfig and cmake modue to wrong place

[ https://issues.apache.org/jira/browse/LOGCXX-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Frost updated LOGCXX-536: Description: While  packaging 0.12.1 for Debian I observed that the install target for the pkgconf

[jira] [Created] (LOGCXX-536) CMakeLists.txt install pgkconfig and cmake modue to wrong place

Tobias Frost created LOGCXX-536: --- Summary: CMakeLists.txt install pgkconfig and cmake modue to wrong place Key: LOGCXX-536 URL: https://issues.apache.org/jira/browse/LOGCXX-536 Project: Log4cxx

[jira] [Commented] (LOGCXX-431) When log4cxx creates a thread, it doesn't block signals it's not using, leading to unreliable signal delivery for the calling process.

[ https://issues.apache.org/jira/browse/LOGCXX-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453817#comment-17453817 ] Tobias Frost commented on LOGCXX-431: - (I'm currently packaging liblog4cxx 0.12.1 for

[CI][SUCCESS] Logging/log4j/release-2.x#405 back to normal

BUILD SUCCESS Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/405/ Project: release-2.x Date of build: Mon, 06 Dec 2021 03:46:59 + Build duration: 1 hr 31 min and counting JUnit Tests Name: (root) Failed: 0 test(s), P

[GitHub] [logging-log4j2] dependabot[bot] commented on pull request #560: Bump maven-core from 3.6.0 to 3.8.2

dependabot[bot] commented on pull request #560: URL: https://github.com/apache/logging-log4j2/pull/560#issuecomment-986419531 Superseded by #610. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to

[GitHub] [logging-log4j2] dependabot[bot] closed pull request #560: Bump maven-core from 3.6.0 to 3.8.2

dependabot[bot] closed pull request #560: URL: https://github.com/apache/logging-log4j2/pull/560 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: n

[GitHub] [logging-log4j2] dependabot[bot] opened a new pull request #610: Bump maven-core from 3.6.0 to 3.8.4

dependabot[bot] opened a new pull request #610: URL: https://github.com/apache/logging-log4j2/pull/610 Bumps [maven-core](https://github.com/apache/maven) from 3.6.0 to 3.8.4. Commits https://github.com/apache/maven/commit/9b656c72d54e5bacbed989b64718c159fe39b537";>9b656c7 [ma

[jira] [Resolved] (LOG4J2-2288) Fix contribution documentation - No such branch nor tag log4j-2.11.0

[ https://issues.apache.org/jira/browse/LOG4J2-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2288. - Resolution: Fixed This was corrected some time ago. > Fix contribution documentation - No such

[jira] [Resolved] (LOG4J2-3078) System property for default configuration file

[ https://issues.apache.org/jira/browse/LOG4J2-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3078. - Resolution: Not A Problem > System property for default configuration file > ---

[jira] [Resolved] (LOG4J2-3166) wrong documentation for logging with Level.OFF

[ https://issues.apache.org/jira/browse/LOG4J2-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-3166. - Fix Version/s: 2.15.0 Resolution: Fixed The data in the table has been corrected. Please

[jira] [Commented] (LOG4J2-3166) wrong documentation for logging with Level.OFF

[ https://issues.apache.org/jira/browse/LOG4J2-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453771#comment-17453771 ] ASF subversion and git services commented on LOG4J2-3166: - Commi

[jira] [Commented] (LOG4J2-3166) wrong documentation for logging with Level.OFF

[ https://issues.apache.org/jira/browse/LOG4J2-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453770#comment-17453770 ] ASF subversion and git services commented on LOG4J2-3166: - Commi

[jira] [Commented] (LOG4J2-656) How to delete rolled over folder older than six months.

[ https://issues.apache.org/jira/browse/LOG4J2-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453743#comment-17453743 ] Remko Popma commented on LOG4J2-656: Hi [~aadit] ! Have you had a chance to look at

[CI][UNSTABLE] Logging/log4j/release-2.x#404 has test failures

BUILD UNSTABLE Build URL https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/404/ Project: release-2.x Date of build: Sun, 05 Dec 2021 21:48:55 + Build duration: 1 hr 33 min and counting JUnit Tests Name: (root) Failed: 0 test(s),

[jira] [Commented] (LOG4J2-656) How to delete rolled over folder older than six months.

[ https://issues.apache.org/jira/browse/LOG4J2-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453731#comment-17453731 ] Aadit Bhojgi commented on LOG4J2-656: - [~rpopma] why was this issue CLOSED? I didn't

[jira] [Resolved] (LOG4J2-2516) log4j2 incompatible with Gradle 5.0

[ https://issues.apache.org/jira/browse/LOG4J2-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2516. - Resolution: Won't Fix I believe Remko's response addresses this issue. The reporter never respon

[jira] [Commented] (LOG4J2-2525) Add max message size limit to JSON Layout

[ https://issues.apache.org/jira/browse/LOG4J2-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453704#comment-17453704 ] Ralph Goers commented on LOG4J2-2525: - JsonLayout is effectively deprecated. You sho

[jira] [Resolved] (LOG4J2-2526) Log4j2 should monitor changes to lookup values

[ https://issues.apache.org/jira/browse/LOG4J2-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2526. - Resolution: Won't Fix This is impractical at best and impossible at worst. "Polling" all registe

[jira] [Resolved] (LOG4J2-2528) Why is 'packages' property needed within Configuration tag

[ https://issues.apache.org/jira/browse/LOG4J2-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2528. - Resolution: Information Provided > Why is 'packages' property needed within Configuration tag >

[jira] [Commented] (LOG4J2-2529) Cannot extend LogPatternConverter

[ https://issues.apache.org/jira/browse/LOG4J2-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453702#comment-17453702 ] Ralph Goers commented on LOG4J2-2529: - I must be missing something. The newInstance

[jira] [Resolved] (LOG4J2-2531) Using method references to Logger methods leads to wrong source file and line number in log entry

[ https://issues.apache.org/jira/browse/LOG4J2-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2531. - Resolution: Won't Fix This is behaving correctly. The call to the Logging API is made from the

[jira] [Commented] (LOG4J2-2536) -> value is output as is

[ https://issues.apache.org/jira/browse/LOG4J2-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453696#comment-17453696 ] Ralph Goers commented on LOG4J2-2536: - It is recommended that all usages of the Json

[jira] [Resolved] (LOG4J2-2540) Incomplete enumeration of logging levels

[ https://issues.apache.org/jira/browse/LOG4J2-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2540. - Fix Version/s: 2.15.0 Resolution: Fixed Patch applied. Please verify and close. > Incomp

[jira] [Commented] (LOG4J2-2540) Incomplete enumeration of logging levels

[ https://issues.apache.org/jira/browse/LOG4J2-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453694#comment-17453694 ] ASF subversion and git services commented on LOG4J2-2540: - Commi

[jira] [Commented] (LOG4J2-2540) Incomplete enumeration of logging levels

[ https://issues.apache.org/jira/browse/LOG4J2-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453693#comment-17453693 ] ASF subversion and git services commented on LOG4J2-2540: - Commi

[jira] [Commented] (LOG4J2-2541) Configuration Syntax – missing section heading for concise format and typo

[ https://issues.apache.org/jira/browse/LOG4J2-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453688#comment-17453688 ] ASF subversion and git services commented on LOG4J2-2541: - Commi

[jira] [Resolved] (LOG4J2-2541) Configuration Syntax – missing section heading for concise format and typo

[ https://issues.apache.org/jira/browse/LOG4J2-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2541. - Fix Version/s: 2.15.0 Resolution: Fixed patch applied. Please verify and close. > Config

[jira] [Commented] (LOG4J2-2541) Configuration Syntax – missing section heading for concise format and typo

[ https://issues.apache.org/jira/browse/LOG4J2-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453687#comment-17453687 ] ASF subversion and git services commented on LOG4J2-2541: - Commi

[jira] [Closed] (LOG4J2-2546) Wrong property mentioned for log4j2.disable.jmx

[ https://issues.apache.org/jira/browse/LOG4J2-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers closed LOG4J2-2546. --- Resolution: Won't Fix Closing this since the documented property works. > Wrong property mentioned

[jira] [Commented] (LOG4J2-2553) TLS syslog appender: doc suggests to use to configure appender

[ https://issues.apache.org/jira/browse/LOG4J2-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453681#comment-17453681 ] ASF subversion and git services commented on LOG4J2-2553: - Commi

[jira] [Resolved] (LOG4J2-2553) TLS syslog appender: doc suggests to use to configure appender

[ https://issues.apache.org/jira/browse/LOG4J2-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2553. - Fix Version/s: 2.15.0 Resolution: Fixed Please verify and close. > TLS syslog appender:

[jira] [Commented] (LOG4J2-2553) TLS syslog appender: doc suggests to use to configure appender

[ https://issues.apache.org/jira/browse/LOG4J2-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453682#comment-17453682 ] ASF subversion and git services commented on LOG4J2-2553: - Commi

[jira] [Resolved] (LOG4J2-1798) InterruptedException on RollingFileManager#rollover()

[ https://issues.apache.org/jira/browse/LOG4J2-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-1798. - Fix Version/s: 2.15.0 Resolution: Fixed Thanks for the patch! It has been applied. Please

[jira] [Commented] (LOG4J2-1798) InterruptedException on RollingFileManager#rollover()

[ https://issues.apache.org/jira/browse/LOG4J2-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453677#comment-17453677 ] ASF subversion and git services commented on LOG4J2-1798: - Commi

[jira] [Commented] (LOG4J2-1798) InterruptedException on RollingFileManager#rollover()

[ https://issues.apache.org/jira/browse/LOG4J2-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453676#comment-17453676 ] ASF subversion and git services commented on LOG4J2-1798: - Commi

[jira] [Resolved] (LOG4J2-2951) Properties are not resolved with Log4J1 configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers resolved LOG4J2-2951. - Fix Version/s: 2.15.0 Resolution: Fixed A patch has been applied. Please verify and close

[jira] [Commented] (LOG4J2-2951) Properties are not resolved with Log4J1 configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453669#comment-17453669 ] ASF subversion and git services commented on LOG4J2-2951: - Commi

[jira] [Commented] (LOG4J2-2951) Properties are not resolved with Log4J1 configuration

[ https://issues.apache.org/jira/browse/LOG4J2-2951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453668#comment-17453668 ] ASF subversion and git services commented on LOG4J2-2951: - Commi

[jira] [Commented] (LOG4J2-1915) Log4j2 version 2.8.2 is not working for android logging

[ https://issues.apache.org/jira/browse/LOG4J2-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453665#comment-17453665 ] Volkan Yazici commented on LOG4J2-1915: --- [~rgoers], agreed, closing it. > Log4j2

[jira] [Closed] (LOG4J2-1915) Log4j2 version 2.8.2 is not working for android logging

[ https://issues.apache.org/jira/browse/LOG4J2-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici closed LOG4J2-1915. - > Log4j2 version 2.8.2 is not working for android logging Happens if we use Log4j2 V2.8.2.> > -

[jira] [Updated] (LOG4J2-2926) Application OUTAGE due to Unable to write to stream TCP

[ https://issues.apache.org/jira/browse/LOG4J2-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici updated LOG4J2-2926: -- Fix Version/s: (was: 2.13.3) > Application OUTAGE due to Unable to write to stream TCP > -

[jira] [Resolved] (LOG4J2-3200) Log4j2 compatibility with Open Telemetry

[ https://issues.apache.org/jira/browse/LOG4J2-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rémi C. resolved LOG4J2-3200. - Resolution: Works for Me > Log4j2 compatibility with Open Telemetry > --

[jira] [Commented] (LOG4J2-2926) Application OUTAGE due to Unable to write to stream TCP

[ https://issues.apache.org/jira/browse/LOG4J2-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453540#comment-17453540 ] Ralph Goers commented on LOG4J2-2926: - I should add to this that the SocketAppender