[
https://issues.apache.org/jira/browse/LOG4J2-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-331.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta9
Fixed in trunk. Please verify (either by compiling trunk or waiting for beta9)
and close.
> “ERROR Failed to write log event to MongoDB due to invalid result [0]” when
> using NoSQLAppender
> -----------------------------------------------------------------------------------------------
>
> Key: LOG4J2-331
> URL: https://issues.apache.org/jira/browse/LOG4J2-331
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.0-beta8
> Environment: JDK 1.7, Mongo Driver 2.11.2
> Reporter: Ruslan
> Assignee: Nick Williams
> Fix For: 2.0-beta9
>
>
> I get following message
> ERROR Failed to write log event to MongoDB due to invalid result [0]
> when using NoSQLAppender with log4j2 v2.0-beta8 but log event gets written to
> MongoDB.
> Here is my config
> {quote}
> <?xml version="1.0" encoding="UTF-8"?>
> <configuration status="WARN">
> <appenders>
> <NoSql name="databaseAppender" suppressExceptions="true">
> <MongoDb collectionName="applicationLog"
> factoryClassName="com.borsch.DBManager" factoryMethodName="getNewMongoClient"
> writeConcernConstant="NONE" username="root" password="qwe"/>
> </NoSql>
> </appenders>
> <loggers>
> <root level="error">
> <appender-ref ref="databaseAppender"/>
> </root>
> </loggers>
> </configuration>
> {quote}
> What's even more strange I can't find the code that generates it. I didn't
> find such string in sources of log4j2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
