Sure, that is just another workaround.
>-Original Message-
>From: ext Bender Heri [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 19, 2006 7:17 PM
>To: Log4J Users List
>Subject: RE: High performance filters
>
>Very nice, indeed, but it doesn't apply to exist
Very nice, indeed, but it doesn't apply to existing logging code neither...
Heri
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 19, 2006 6:33 PM
> To: log4j-user@logging.apache.org
> Subject: RE: High perfor
.apache.org
>Subject: RE: High performance filters
>
>After an extra look at log4j source I wonder if I've found
>some kind of solution:
>Logger contains the following signature:
>log.debug(Object message)
>
>Here this is an "Ojbject" and not a "String".
at solution.
What do you guys think about it?
>-Original Message-
>From: ext James Stauffer [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 19, 2006 5:44 PM
>To: Log4J Users List
>Subject: Re: High performance filters
>
>It would really only work with 1 extra criteria
rver, that would create a huge number of
loggers. Do you have any idea about performance impact?
>-Original Message-
>From: ext James Stauffer [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 19, 2006 5:22 PM
>To: Log4J Users List
>Subject: Re: High performance filters
>
>
sage, which is quite CPU intensive.
>-Original Message-
>From: ext James Stauffer [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 19, 2006 5:26 PM
>To: Log4J Users List
>Subject: Re: High performance filters
>
>Another option would be to write your own appender wh
ilto:[EMAIL PROTECTED]
>Sent: Wednesday, July 19, 2006 5:22 PM
>To: Log4J Users List
>Subject: Re: High performance filters
>
>One option would be to include to the IP address in the logger name.
>Logger log = Logger.getLogger(getClass().getName() + "." +
>request.getS
nsive.
>-Original Message-
>From: ext James Stauffer [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 19, 2006 5:26 PM
>To: Log4J Users List
>Subject: Re: High performance filters
>
>Another option would be to write your own appender which
>filters before creating the message
ks for your help,
Vincent.
>-Original Message-
>From: ext Javier Gonzalez [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 19, 2006 5:08 PM
>To: Log4J Users List
>Subject: Re: High performance filters
>
>On 7/19/06, [EMAIL PROTECTED]
><[EMAIL PROTECTED]> wrote:
&
55 PM
> To: log4j-user@logging.apache.org
> Subject: RE: High performance filters
>
>
> I'm not sure your proposal solves my problem.
> I'm sorry if my question was not clear enough. Let me try another way:
>
> Considering the following code snippet
>
> /
st) call) which is still quite
expensive (and useless in this context).
I hope this is clear enough :)
Thanks a lot for your time!
Vincent.
>-Original Message-
>From: ext Javier Gonzalez [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 19, 2006 3:44 PM
>To: Log4J Users
log4j-compliant code :(
I'll ask to the dev mailing list, just in case...
Thanks for your help,
Vincent.
>-Original Message-
>From: ext Javier Gonzalez [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 19, 2006 5:08 PM
>To: Log4J Users List
>Subject: Re: High perform
On 7/19/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I hope this is clear enough :)
It is, and your problem looks very non-trivial :)
To me, it looks like you need to implement your own filtering before
invoking buildDebugMessage(), since to access the log4j framework you
need to pass an o
e
expensive (and useless in this context).
I hope this is clear enough :)
Thanks a lot for your time!
Vincent.
>-Original Message-
>From: ext Javier Gonzalez [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, July 19, 2006 3:44 PM
>To: Log4J Users List
>Subject: Re: Hig
Create separate Loggers for the debug requests, and leave only those
loggers at debug level. Then prepend log.debug() calls with
if(log.isDebugEnabled()), so that the debug messages will only be
created if the particular logger is debug enabled.
(I'm not sure I understood your question correctly,
Hi all,
I'm building some kind of server and I use log4j for logging.
For troubleshooting issue I whant to be able to debug some few requests
only (based on matching criterias) so that it is possible to debug live
servers without killing performances.
I managed to use NDC and filters to do that a
16 matches
Mail list logo
