/browse/LOG4J2-222 for
this. I will take a look and see what I can do. This may take some time.
Best regards,
Remko
--
*From:* Steven Yang kenshin...@gmail.com
*To:* Remko Popma rem...@yahoo.com
*Sent:* Sunday, April 28, 2013 9:43 AM
*Subject:* Re: How to use
Hi,
FastFile appenders are buffered.
You won't see output in the log file until you log a lot.
To see output immediately you should either specify immediateFlush=true or use
Async Loggers or AsynchAppender (they will auto-flush efficiently).
Hope this helps,
Remko
Sent from my iPhone
On
Two more things:
disruptor 3.0.1 is fine.
Your layout pattern doesn't actually use location, so if you use Async (Logger
or Appender) I'd recommend you set includeLocation=false for better
performance.
Remko
Sent from my iPhone
On 2013/04/27, at 18:59, Remko Popma rem...@yahoo.com wrote:
(Including Steven in recipients)
Sent from my iPhone
On 2013/04/27, at 19:06, Remko Popma rem...@yahoo.com wrote:
Two more things:
disruptor 3.0.1 is fine.
Your layout pattern doesn't actually use location, so if you use Async
(Logger or Appender) I'd recommend you set
Thanks Remko for the comment
Ok I now understand why I dont see the log.
I am running in a tomcat, but when I shutdown my web server I dont see log
being flushed out to file.
Does that mean even when I run my application for a while and even after
some logs are flushed out then I shutdown my
Steven,
In your config, instead of root, try asyncRoot. You need the disruptor jar
on the classpath. This will result in events being flushed to disk immediately,
but in an efficient way: in batches, not one by one.
I need to take a look at the behavior on Tomcat shutdown. There is a shutdown
From: Steven Yang kenshin...@gmail.com
To: Remko Popma rem...@yahoo.com
Sent: Sunday, April 28, 2013 9:43 AM
Subject: Re: How to use FastFile
Thanks, I tried using asyncRoot and everything seems to log fine and I do see a
lot of logs.
And logs do seem to be flushed immediately
