[jira] [Resolved] (LOGCXX-549) Make networking classes independent of implementation

[ https://issues.apache.org/jira/browse/LOGCXX-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Middleton resolved LOGCXX-549. - Resolution: Fixed > Make networking classes independent of implementat

[jira] [Resolved] (LOGCXX-527) Mock the clock for tests

[ https://issues.apache.org/jira/browse/LOGCXX-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Middleton resolved LOGCXX-527. - Resolution: Fixed > Mock the clock for te

[jira] [Updated] (LOGCXX-451) Application hang up during exit on Windows

[ https://issues.apache.org/jira/browse/LOGCXX-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Middleton updated LOGCXX-451: Fix Version/s: 1.0.0 > Application hang up during exit on Wind

[jira] [Updated] (LOGCXX-432) AsyncAppender automatically switches to sync mode when e.g. there is no disk space available

[ https://issues.apache.org/jira/browse/LOGCXX-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Middleton updated LOGCXX-432: Fix Version/s: 1.0.0 > AsyncAppender automatically switches to sync mode when

[jira] [Resolved] (LOGCXX-432) AsyncAppender automatically switches to sync mode when e.g. there is no disk space available

[ https://issues.apache.org/jira/browse/LOGCXX-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Middleton resolved LOGCXX-432. - Resolution: Fixed > AsyncAppender automatically switches to sync mode when

[jira] [Updated] (LOG4J2-3605) log4j-to-slf4j: add runtime logback-classic dependency

[ https://issues.apache.org/jira/browse/LOG4J2-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piotr Karwasz updated LOG4J2-3605: -- Description: Since users expect the SLF4J-to-Log4j2 bridge to have a runtime dependency

[jira] [Created] (LOG4J2-3605) log4j-to-slf4j: add runtime logback-classic dependency

Piotr Karwasz created LOG4J2-3605: - Summary: log4j-to-slf4j: add runtime logback-classic dependency Key: LOG4J2-3605 URL: https://issues.apache.org/jira/browse/LOG4J2-3605 Project: Log4j 2

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608534#comment-17608534 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608529#comment-17608529 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608533#comment-17608533 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608532#comment-17608532 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608530#comment-17608530 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608531#comment-17608531 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608535#comment-17608535 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608527#comment-17608527 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608528#comment-17608528 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608526#comment-17608526 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608518#comment-17608518 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608523#comment-17608523 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608524#comment-17608524 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608515#comment-17608515 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608512#comment-17608512 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608522#comment-17608522 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608516#comment-17608516 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608517#comment-17608517 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608519#comment-17608519 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608510#comment-17608510 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608508#comment-17608508 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608513#comment-17608513 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608503#comment-17608503 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608507#comment-17608507 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608506#comment-17608506 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608520#comment-17608520 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608514#comment-17608514 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608521#comment-17608521 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608525#comment-17608525 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608504#comment-17608504 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608501#comment-17608501 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608505#comment-17608505 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608509#comment-17608509 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608511#comment-17608511 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608502#comment-17608502 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608496#comment-17608496 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608498#comment-17608498 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608494#comment-17608494 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608500#comment-17608500 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608493#comment-17608493 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608497#comment-17608497 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608499#comment-17608499 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608495#comment-17608495 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Comment Edited] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608234#comment-17608234 ] Robbie Gemmell edited comment on LOG4J2-3601 at 9/22/22 12:11 PM: -- I

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17608234#comment-17608234 ] Robbie Gemmell commented on LOG4J2-3601: I came to report this, but am not surprised to see

[jira] [Comment Edited] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607371#comment-17607371 ] Andy Seaborne edited comment on LOG4J2-3601 at 9/22/22 9:31 AM: We have

[jira] [Created] (LOG4J2-3604) Log4j 1.2 Bridge not printing exception stack traces

Vidya created LOG4J2-3604: - Summary: Log4j 1.2 Bridge not printing exception stack traces Key: LOG4J2-3604 URL: https://issues.apache.org/jira/browse/LOG4J2-3604 Project: Log4j 2 Issue Type: Bug

[jira] [Commented] (LOG4J2-3603) Provide a lightweight alternative to Spring's LoggingSystem

[ https://issues.apache.org/jira/browse/LOG4J2-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607870#comment-17607870 ] Matt Sicker commented on LOG4J2-3603: - This would be essentially some sort of bootstrap code

[jira] [Commented] (LOG4J2-3603) Provide a lightweight alternative to Spring's LoggingSystem

[ https://issues.apache.org/jira/browse/LOG4J2-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607866#comment-17607866 ] Piotr Karwasz commented on LOG4J2-3603: --- [~rgoers], Basically I am proposing to use Matt's

[jira] [Commented] (LOG4J2-3603) Provide a lightweight alternative to Spring's LoggingSystem

[ https://issues.apache.org/jira/browse/LOG4J2-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607821#comment-17607821 ] Ralph Goers commented on LOG4J2-3603: - I don't really understand this issue. The LoggingSystem only

[jira] [Created] (LOG4J2-3603) Provide a lightweight alternative to Spring's LoggingSystem

Piotr Karwasz created LOG4J2-3603: - Summary: Provide a lightweight alternative to Spring's LoggingSystem Key: LOG4J2-3603 URL: https://issues.apache.org/jira/browse/LOG4J2-3603 Project: Log4j 2

[jira] [Commented] (LOG4J2-3602) Don't output ERROR level stacktrace in getLogger() call when there is no network available

[ https://issues.apache.org/jira/browse/LOG4J2-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607375#comment-17607375 ] Piotr Karwasz commented on LOG4J2-3602: --- Hi [~lou...@broadinstitute.org], Thank you for reporting

[jira] [Comment Edited] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607371#comment-17607371 ] Andy Seaborne edited comment on LOG4J2-3601 at 9/20/22 7:18 PM: We have

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607371#comment-17607371 ] Andy Seaborne commented on LOG4J2-3601: --- We have the internal (clean separation of api, core

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607343#comment-17607343 ] Christopher Tubbs commented on LOG4J2-3601: --- Yes, technically, for maximum user choice

[jira] [Comment Edited] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607291#comment-17607291 ] Ralph Goers edited comment on LOG4J2-3601 at 9/20/22 4:25 PM: -- I

[jira] [Comment Edited] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607291#comment-17607291 ] Ralph Goers edited comment on LOG4J2-3601 at 9/20/22 4:24 PM: -- I

[jira] [Comment Edited] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607291#comment-17607291 ] Ralph Goers edited comment on LOG4J2-3601 at 9/20/22 4:21 PM: -- I

[jira] [Comment Edited] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607291#comment-17607291 ] Ralph Goers edited comment on LOG4J2-3601 at 9/20/22 4:19 PM: -- I

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607291#comment-17607291 ] Ralph Goers commented on LOG4J2-3601: - I was incorrect when I looked at Log4jLoggerFactory. log4j

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17607206#comment-17607206 ] Andy Seaborne commented on LOG4J2-3601: --- Hi [~pkarwasz], One of the things Jena provides

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606784#comment-17606784 ] Ralph Goers commented on LOG4J2-3601: - [~pkarwasz] I originally thought the log4j-core should

[jira] [Comment Edited] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606783#comment-17606783 ] Piotr Karwasz edited comment on LOG4J2-3601 at 9/19/22 10:09 PM

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606783#comment-17606783 ] Piotr Karwasz commented on LOG4J2-3601: --- [~ctubbsii], The reason I didn't put {{log4j-core

[jira] [Updated] (LOG4J2-3602) Don't output ERROR level stacktrace in getLogger() call when there is no network available

[ https://issues.apache.org/jira/browse/LOG4J2-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Louis Bergelson updated LOG4J2-3602: Description: If there is no network adaptor trying to get a new logger using

[jira] [Created] (LOG4J2-3602) Don't output ERROR level stacktrace in getLogger() call when there is no network available

Louis Bergelson created LOG4J2-3602: --- Summary: Don't output ERROR level stacktrace in getLogger() call when there is no network available Key: LOG4J2-3602 URL: https://issues.apache.org/jira/browse/LOG4J2-3602

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606750#comment-17606750 ] Christopher Tubbs commented on LOG4J2-3601: --- [~pkarwasz] It does not make sense to use log4j

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606725#comment-17606725 ] Piotr Karwasz commented on LOG4J2-3601: --- [~andy], Thank you for reporting this issue. Personally

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606714#comment-17606714 ] Ralph Goers commented on LOG4J2-3601: - Note that we don't assign fix versions until the fix

[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-3601: Affects Version/s: 2.19.0 > log4j-slf4j2: change of dependency scope for log4j-c

[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralph Goers updated LOG4J2-3601: Fix Version/s: (was: 2.19.0) > log4j-slf4j2: change of dependency scope for log4j-c

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606713#comment-17606713 ] Christopher Tubbs commented on LOG4J2-3601: --- FWIW, the fix version is incorrect. 2.19.0

[jira] [Comment Edited] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606710#comment-17606710 ] Christopher Tubbs edited comment on LOG4J2-3601 at 9/19/22 6:37 PM

[jira] [Commented] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606710#comment-17606710 ] Christopher Tubbs commented on LOG4J2-3601: --- This bit us when we tried to update to slf4j

[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated LOG4J2-3601: -- Description: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core

[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated LOG4J2-3601: -- Description: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core

[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated LOG4J2-3601: -- Description: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606346#comment-17606346 ] ASF subversion and git services commented on LOG4J2-3188: - Commit

[jira] [Closed] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volkan Yazici closed LOG4J2-3188. - Assignee: Volkan Yazici Resolution: Not A Problem > Concurrent individual LoggerCont

[jira] [Commented] (LOG4J2-3188) Concurrent individual LoggerContext initializations cause severe LogEvent drop or incorrect delivery

[ https://issues.apache.org/jira/browse/LOG4J2-3188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606344#comment-17606344 ] Volkan Yazici commented on LOG4J2-3188: --- {{Configurator.initialize(Configuration)}} sets

[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated LOG4J2-3601: -- Description: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core

[jira] [Updated] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne updated LOG4J2-3601: -- Description: The artifact {{log4j-slf4j-impl}} has a scope=runtime dependency on log4j-core

[jira] [Created] (LOG4J2-3601) log4j-slf4j2: change of dependency scope for log4j-core

Andy Seaborne created LOG4J2-3601: - Summary: log4j-slf4j2: change of dependency scope for log4j-core Key: LOG4J2-3601 URL: https://issues.apache.org/jira/browse/LOG4J2-3601 Project: Log4j 2

[jira] [Commented] (LOG4J2-3564) NPE in JULLogger.getLevel()

[ https://issues.apache.org/jira/browse/LOG4J2-3564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606182#comment-17606182 ] ASF subversion and git services commented on LOG4J2-3564: - Commit

[jira] [Commented] (LOG4J2-708) Servlet filter claims to support async but doesn't use AsyncContext

[ https://issues.apache.org/jira/browse/LOG4J2-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17606181#comment-17606181 ] ASF subversion and git services commented on LOG4J2-708: Commit

[jira] (LOG4J2-3370) Add Support for SLF4J 2.0

[ https://issues.apache.org/jira/browse/LOG4J2-3370 ] Christopher Tubbs deleted comment on LOG4J2-3370: --- was (Author: ctubbsii): SLF4J 2.0.1 is released. This says fixed in 2.19.0, but no such release yet exists. Please release 2.19.0

[jira] [Commented] (LOG4J2-3139) Startup errors with SLF4J 2.0.0-alpha4

[ https://issues.apache.org/jira/browse/LOG4J2-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605898#comment-17605898 ] Ralph Goers commented on LOG4J2-3139: - [~ctubbsii] Please review the dev list before asking

[jira] [Commented] (LOG4J2-3370) Add Support for SLF4J 2.0

[ https://issues.apache.org/jira/browse/LOG4J2-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605897#comment-17605897 ] Ralph Goers commented on LOG4J2-3370: - [~ctubbsii] Please review the dev list before asking

[jira] [Updated] (LOG4J2-3600) ERROR Unable to locate plugin type for ClogAppenderFilter

[ https://issues.apache.org/jira/browse/LOG4J2-3600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Poornima updated LOG4J2-3600: - Description: Getting below error. Tried many options from google, nothing is working ^2022-09-16 15:57

[jira] [Created] (LOG4J2-3600) ERROR Unable to locate plugin type for ClogAppenderFilter

Poornima created LOG4J2-3600: Summary: ERROR Unable to locate plugin type for ClogAppenderFilter Key: LOG4J2-3600 URL: https://issues.apache.org/jira/browse/LOG4J2-3600 Project: Log4j 2 Issue

[jira] [Commented] (LOG4J2-3139) Startup errors with SLF4J 2.0.0-alpha4

[ https://issues.apache.org/jira/browse/LOG4J2-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605604#comment-17605604 ] Piotr Karwasz commented on LOG4J2-3139: --- [~ctubbsii], The release process of Apache projects

[jira] [Commented] (LOG4J2-3370) Add Support for SLF4J 2.0

[ https://issues.apache.org/jira/browse/LOG4J2-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605600#comment-17605600 ] Christopher Tubbs commented on LOG4J2-3370: --- SLF4J 2.0.1 is released. This says fixed

[jira] [Commented] (LOG4J2-3139) Startup errors with SLF4J 2.0.0-alpha4

[ https://issues.apache.org/jira/browse/LOG4J2-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17605599#comment-17605599 ] Christopher Tubbs commented on LOG4J2-3139: --- SLF4J 2.0.1 is released. This says fixed

<    5   6   7   8   9   10   11   12   13   14   >