That is strange: with the async appender (and also with async loggers),
Log4j2 should automatically flush the I/O buffer when the async queue is
empty...
You may have found an issue. Can you raise a JIRA ticket for this?
Meanwhile, you can add attribute immediateFlush="true" to your Rolling
file
Cool! Stay in touch: ideas are always welcome!
On Fri, Nov 24, 2017 at 3:41 AM, Enric Jaen
wrote:
> I will try it and let you know
> best regards
> Enric
>En jueves, 23 de noviembre de 2017 12:37:25 GMT, Remko Popma <
> remko.po...@gmail.com> escribió:
>
> You know, I think we may already h
The Apache Log4j 2 team is pleased to announce the Log4j 2.10.0 release!
Apache Log4j is a well known framework for logging application behavior. Log4j
2 is an upgrade to Log4j that provides significant improvements over its
predecessor, Log4j 1.x, and provides many other modern features such as
I will try it and let you know
best regards
Enric
En jueves, 23 de noviembre de 2017 12:37:25 GMT, Remko Popma
escribió:
You know, I think we may already have something very similar...
Take a look at the second example under Map Filter:
https://logging.apache.org/log4j/2.x/manual/filters.
It seems you are trying to create an asynchronous root logger. For that you
need to use AsyncRoot, not AsyncLogger.
Ralph
> On Nov 23, 2017, at 7:37 AM, Laurent Hasson wrote:
>
>
> I saw on the log4j site
> (https://logging.apache.org/log4j/2.x/manual/async.html) that async loggers
> were p
thanks!
On Thu, Nov 23, 2017 at 11:33 AM, Mikael Ståldal wrote:
> Log4j 2 has properties based configuration (since version 2.4), but it is
> a different format than Log4j 1.x, not compatible.
>
> https://logging.apache.org/log4j/2.x/manual/configuration.html#Properties
>
>
> On 2017-11-23 14:00
Log4j 2 has properties based configuration (since version 2.4), but it
is a different format than Log4j 1.x, not compatible.
https://logging.apache.org/log4j/2.x/manual/configuration.html#Properties
On 2017-11-23 14:00, Alex O'Ree wrote:
Did log4j 2 drop support for the properties based confi
There is a compatibility layer for v1.2 prop file. You have to call it
explicitly though. I am AFK so you'll have to dig in to do it.
Gary
On Nov 23, 2017 08:00, "Alex O'Ree" wrote:
> Did log4j 2 drop support for the properties based configuration file?
>
Hello all,
I have the following configuration file using async appenders. It works well
but I have one issue. During low-volume activity on my site, it seems that
nothing is output to the file, so it's hard to see what's going on. Same issue
happens while developing. But as soon as enough activ
I saw on the log4j site
(https://logging.apache.org/log4j/2.x/manual/async.html) that async loggers
were preferred performance-wise to async appenders. It describes a way to get
async loggers through system properties, but I as trying to get that done
through the configuration file. I tried th
Did log4j 2 drop support for the properties based configuration file?
You know, I think we may already have something very similar...
Take a look at the second example under Map Filter:
https://logging.apache.org/log4j/2.x/manual/filters.html#MapFilter
If you use a RegexFilter (
https://logging.apache.org/log4j/2.x/manual/filters.html#RegexFilter) would
that meet yo
Hi, Sometimes it happens that we want to see logs from a class, but not all
logs as it can be verbose. I think it would useful to be able to filter logs
inside a logger, specially when the logger is class.
For example we could use include and exclude regexps:
or
Running my main application in Eclipse it is using the log4j2-test.xml
configuration, and not the log4j2.xml configuration.
src/main/resources/log4j2.xml
src/test/resources/log4j2-test.xml
I am not running a test application under src/test, but my main application
under src/main/
target/classes/l
14 matches
Mail list logo
