20:53
To: Log4J Users List
Subject: Re: includeLocation = true by default in LoggerConfig
Aha!
Can we take a look at the source for this extension?
Remko
Sent from my iPhone
> On 2014/12/02, at 1:26, "Yair Ogen (yaogen)" wrote:
>
> I am using a custom extension of the asyn
t; To: Log4J Users List
> Subject: Re: includeLocation = true by default in LoggerConfig
>
> Yair, are you using Async Loggers or AsyncAppender?
> Can you give us your full configuration file?
>
> On Tue, Dec 2, 2014 at 12:22 AM, Gary Gregory
> wrote:
>
>> It l
Remko Popma [mailto:remko.po...@gmail.com]
Sent: Monday, December 01, 2014 17:32
To: Log4J Users List
Subject: Re: includeLocation = true by default in LoggerConfig
Yair, are you using Async Loggers or AsyncAppender?
Can you give us your full configuration file?
On Tue, Dec 2, 2014 at 12:22 AM,
Yair, are you using Async Loggers or AsyncAppender?
Can you give us your full configuration file?
On Tue, Dec 2, 2014 at 12:22 AM, Gary Gregory
wrote:
> It looks like you'd dropped the message thread from your reply (don't do
> that please).
>
> What version are you using?
>
> Gary
>
> On Mon, D
2.1
-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com]
Sent: Monday, December 01, 2014 17:23
To: Log4J Users List
Subject: Re: includeLocation = true by default in LoggerConfig
It looks like you'd dropped the message thread from your reply (don't do th
It looks like you'd dropped the message thread from your reply (don't do
that please).
What version are you using?
Gary
On Mon, Dec 1, 2014 at 10:18 AM, Yair Ogen (yaogen)
wrote:
> We are using async and calcLocation is the exact method we've seen in the
> profiler.
>
> When initiation the log
We are using async and calcLocation is the exact method we've seen in the
profiler.
When initiation the logger config properly - i.e. the flag set to false - the
calc method disappeared.
The initial value of this flag is only part of the picture and you should
not draw too many conclusions from it.
Log4j2 is very careful about avoiding this overhead.
When logging synchronously, log4j2 will postpone taking a snapshot of the
call stack until the last possible moment: the moment tha
Copied from "LoggerConfig" Source:
private boolean includeLocation = true;
so if I don't override this is on, and I indeed this this consuming CPU in
profiling.
Am I missing something here?
IncludeLocation is false by default:
* For synchronous logging, the expensive operation (taking a stack trace
snapshot) is only performed if the pattern configuration needs it (has some
location parameters as you indicated). If the pattern configuration does
not have location parameters then locat
10 matches
Mail list logo
