Re: [log4j] MongoDB Appender changes heads up.

The build should run as is. If you want to run the MongoDB tests, then build with Java 8. Otherwise, these tests will be skipped. Previously, the MongoDB tests were all annotated with @Ignore, so we are better off now IMO. Gary On Wed, Jan 10, 2018 at 10:04 PM, Ralph Goers wrote: > So now we ne

Re: [log4j] MongoDB Appender changes heads up.

So now we need Java 7, 8 and 9 to perform a build? Did you update the build documentation? Is that the only tool available to test MongoDB? Ralph > On Jan 10, 2018, at 8:18 PM, Gary Gregory wrote: > > The changes are both binary compatible and behavior compatible. The new > code kicks in only

Re: [log4j] MongoDB Appender changes heads up.

The changes are both binary compatible and behavior compatible. The new code kicks in only if the NoSqlAppender node contains a MessageLayout child, which was not possible before. I also added some code to test against an embedded MongoDB instance by using code from de.flapdoodle.embed.mongo. This

Re: [log4j] MongoDB Appender changes heads up.

No objection, but please do this in a way that existing users of this appender are not affected. So if the new behavior is incompatible with the current behavior, then the new behavior should be switched on explicitly in configuration. Remko (Shameless plug) Every java main() method deserve

[log4j] MongoDB Appender changes heads up.

Hi All: I need for the MongoDB Appender to behave similarly to the JMS Appender regarding MapMessages. What I plan on doing: Like with the JMS Appender, if the MongoDB element contains a child MessageLayout element, the MongoDB appender will apply this layout. Like with the JMS Appender, my goa

Re: [jira] [Commented] (LOG4J2-2124) Cannot deploy application that contains Log4j 2.9.x to weblogic server due to com.objectweb.asm.ClassReader errors

This update was made against issues-test.apache.org/jira , not the real lira instance. I don’t see the update at issues.apache.org/jira so the update is going to be ignored. Ralph > On Jan 10, 2018, at 2:26 PM, KT Mack (JIRATE

[LOG4J] Log4j2 is not embeddable due to its system classloader usage

Hi All: Looking for additional community feedback for https://issues.apache.org/jira/browse/LOG4J2-2171 Gary

Re: Event batch

Yes, all async logging, either with AsyncAppender or with Async Loggers will set `endOfBatch` to true on all events where the queue becomes empty. (Shameless plug) Every java main() method deserves http://picocli.info > On Jan 10, 2018, at 19:17, Mikael Ståldal wrote: > > And the same applies

Re: Event batch

And the same applies to AsyncAppender, right? On 2018-01-10 00:14, Remko Popma wrote: Log4j2 internally uses this with async logging: with async logging, the “producer” is the async logging queue. The queue “knows“ whether it’s empty or whether more events will follow immediately and it will s