a yes, there is one difference in your config and the one I
demonstrated for the individual class:
additivity="false"
Sorry - I didn't explain this earlier. But, Paul seems to have touched
on it in his reply. So you should be set :)
-Scott Heaberlin
> ---
-Scott Heaberlin
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Song
> Sent: Monday, December 08, 2003 7:48 PM
> To: [EMAIL PROTECTED]
> Subject: Can we control the logging level to class level
> instead of package level?
>
>
> Hi
leton class which retrieves (and stores) the local
hostname and IP, something we didn't want to determine every time a
request came in.
MDC.put("server.name", currentServerName);
MDC.put("server.ip", currentServerIP);
-Scott Heaberlin
> -Original Message-
>
Note that the StackTraceElement class requires j2se
1.4+.
-Scott Heaberlin
--- Fergus Gallagher <[EMAIL PROTECTED]>
wrote:
> In special circumstances you might want each line of
> the stacktrace to be
> full log lines (i.e., with loglevel, MDC,
> threadname, etc). In this
log4j site. I am glad to see it has already made it to the log4j
articles section of the site.
-Scott Heaberlin
> -Original Message-
> From: Paul Smith [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 13, 2003 5:54 PM
> To: Log4J Users List
> Subject: Re: Instant Loggi
whoops! Of course, now that I re-read the archived post, I see that the
author of the ibm.com article and the person who submitted IMAppender to
the mailing list are one and the same.
I shall slink now back into my troll status...
-Scott
---
d at runtime whose filters
would allow only that/those particular MDC value(s) but would
essentially circumvent the default level filter and allow, say debug
messages.
Just a thought,
-Scott Heaberlin
-
To unsubscribe, e-m
I do know that LoggingEvents are serializable... one way (albeit if
there are other mechanisms I'd prefer them) to clone an instance would
be to serialize then deserialize...
-Scott Heaberlin
-
To unsubscribe, e-mail: [
7;ll read up on the submissions
doc on the site and get to crackin'.
-Scott Heaberlin
> -Original Message-
> From: Yoav Shapira [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2003 7:24 PM
> To: Log4J Users List
> Subject: RE: Fallback Error Handler behavior
> request URIs in your application. Do the
> server-side classes use the
> same approach? What about classes that are not
> servlets, or otherwise
> don't have access to the Request object? Do they
> not log, or do they
> use FQCN?
>
> Just curious, as I haven
ser's sessionId and other data into the MDC.
As far as actual logging statements, we hope to move to log4j taglibs in
the future.
Hope this helps,
-Scott Heaberlin
> -Original Message-
> From: Scott Burns [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 17, 2003 10:59 P
; behavior
you'll have to implement your own custom ErrorHandler (it's not that
difficult though - one of my favorite aspects of Log4J is its design -
the simplicity of implementing/extending the Interfaces and base classes
to achieve exactly the functionality your enterprise requires.
manager reasons.
The log4j developers for the most part are happy to accommodate
suggestions such as yours to the log4j project, especially those which
would improve the design or implementation for all users.
-Scott Heaberlin
bute log output to
several files based on NDC and MDC values. I was pleasantly surprised
to see similar ones added to the log4j-sandbox in recent months.
-Scott Heaberlin
> -Original Message-
> From: Ramadoss Chinnakuzhandai
> [mailto:[EMAIL PROTECTED]
> Sent: Thursday
f application A, but this alone doesn't achieve our
goal of having separate logs per application.
Separate appenders can output to different places via
different methods, but can we somehow specify which
appender to use through each execution c
15 matches
Mail list logo