Hi All:

I get this garbled StatusLogger output when running Mongo tests from Maven:

[INFO] Running org.apache.logging.log4j.mongodb3.MongoDbMapMessageTest
ERREERORRROOR StatusLogger No Log4j 2 configuration file founRd. UsingR
defau StatusLogger No Log4j 2 configuration file found.lt configuration
(logging only errors to the conStatusLogger No Log4j 2 configuration file
found. Using default configursole), Using default configuration (logging
only errors to the console), or user programmatically provided
configurations. Set system or user programmataic ptioraopertyn (loglly
providegi 'log4j2ng d conly errors to the console), onfigurations. Set
system property 'log4j2.debug' .dor useretb pruogo'  tgroshowa L ommg4j 2
show Log4j atiica2 internal initialization logging. See
https://lolntgelyrnging.apache.org/log4j/2.x/manual/configuration.html for
instructal initialization logging. See https://loggi provided
configurations.  internal initialization loggin4j/2.x/manual/configurations
on how to conion.htmperty 'log4j2.debug' to show Log4j 2lfigure Log4j 2
 for instructions on how to configure Log4j 2
g. See https://logging.apache.org/log4j/2.x/manual/configuration.html for
instructions on how to configure Log4j 2
2018-06-26 13:58:45,760 main ERR2018-06-26 13:58:46,632 main ERROR
Recursive call to appenderOR Recursive call to appender MongoDbAppender
2018-06-26 13:58:46,708 main ERROR Recursive call to appender
MongoDbAppender
 MongoDbAppender
2018-06-26 13:58:45,880 main ERROR Recursive call to appender
MongoDbAp2018-06-26 13:58:46,736 main ERROR Recursive call to appender
MongoDbAppender
pender
2

Does the StatusLogger lock the console stream?

Gary

Reply via email to