You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/02/28 15:03:00 UTC
[jira] [Work logged] (LOG4J2-3122) Logging to Log4j2 MongoDb4 Appender get ERROR on trace, debug and info level.
[ https://issues.apache.org/jira/browse/LOG4J2-3122?focusedWorklogId=848090&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-848090 ]
ASF GitHub Bot logged work on LOG4J2-3122:
------------------------------------------
Author: ASF GitHub Bot
Created on: 28/Feb/23 15:02
Start Date: 28/Feb/23 15:02
Worklog Time Spent: 10m
Work Description: vy closed pull request #564: LOG4J2-3122 fix Logging to Log4j2 MongoDb4 Appender get ERROR on trace, debug and info level.
URL: https://github.com/apache/logging-log4j2/pull/564
Issue Time Tracking
-------------------
Worklog Id: (was: 848090)
Remaining Estimate: 0h
Time Spent: 10m
> Logging to Log4j2 MongoDb4 Appender get ERROR on trace, debug and info level.
> -----------------------------------------------------------------------------
>
> Key: LOG4J2-3122
> URL: https://issues.apache.org/jira/browse/LOG4J2-3122
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.14.1
> Reporter: Red Apple
> Priority: Blocker
> Fix For: 2.17.0
>
> Attachments: log4j2-mongodb4-appender-main.zip
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Logging to Log4j2 MongoDb4 Appender on trace, debug and info log level give the following error
> *ERROR Recursive call to appender*
> but give success result and the log got written to the mongodb database when using warn or error log level.
> Possibly something recursive call happens with info log level that causing this bug.
> [Here is the repository|https://github.com/redapel/log4j2-mongodb4-appender] that contain the very minimal code to reproduce the error. The configuration is provided in the *log4j2.xml* file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)