Hello,
According to the performance charts in the documentation, log4j2 has a
significantly higher throughput when using AsyncLoggerContextSelector than
when using all async loggers with any different selector.
Why is that? Is it just because the same context is always reused and
there's no
The manual still has a few places where the packages attribute for custom
plugins is mentioned:
* Configuration Configuration with XML (both in the table and in the
strict XML example)
* Configuration Configuration with Jason (the first example and the
second (Routing) example)
* Configuration
Okay. Let's check to make sure, because we should document it if it does
not work.
I'll look at Eclipse. Any candidates for checking Intelli/J and NetBeans?
On Sat, Jul 19, 2014 at 1:11 AM, Matt Sicker boa...@gmail.com wrote:
Depends on if the IDE is doing anything funky. Starting with Java
It would be a good idea to verify it in IntelliJ, Eclipse and NetBeans.
Ralph
On Jul 18, 2014, at 9:11 AM, Matt Sicker boa...@gmail.com wrote:
Depends on if the IDE is doing anything funky. Starting with Java 1.6,
annotation processing is enabled by default for any processors on the
The Async Loggers created with the context selector have a slightly
different mechanism. One of the differences is that LogEvent objects are
re-used.
However, unless your application is in the low-latency space, I would not
worry too much about the performance difference. Both flavors of Async
