You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by GitBox <gi...@apache.org> on 2021/08/26 18:46:05 UTC

[GitHub] [logging-log4j2] redapel commented on pull request #564: LOG4J2-3122 fix Logging to Log4j2 MongoDb4 Appender get ERROR on trace, debug and info level.

redapel commented on pull request #564:
URL: https://github.com/apache/logging-log4j2/pull/564#issuecomment-906654798


   Hi team, 
   Please have take a look to the new test case that i submitted. In that test, i choose to use real MongoDB server instead of the Flapdoodle's embedded MongoDB as the later can't be considered as "full integration testing", there are possibilities that both of them behaves differently, so it is better to use solution like docker container. By the way, i run the test using a replica set cluster with only single server act as a PRIMARY. I suggest you to run the test more than one (for example 10 times), Since there are at least 2 different error cases produced when i try to test it. Both of them i already made an assertion to fail the test. Let me know about the progress.
   Thanks.


-- 
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: notifications-unsubscribe@logging.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org