>
> The one thing that we did abstract for log4j client code is the
> acquisition
> of the Logger instance (see below). Despite the advice to the contrary
> we
> found that we needed at least thread-specific logging control in some
> circumstances, so storing the Logger instance in a static or in
Matt
> I would like to decouple my classes from the log4j api and was
> considering
My main comment would be to really think through the possible benefits before
doing this. We considered it, but in the end decided that:
i) the Log4J API was well abstracted anyhow, so what would we gain?
ii)
Thanks Jeff. All good thoughts.
-- Rob
Send reply to: "Log4J Users List" <[EMAIL PROTECTED]>
Date sent: Mon, 22 Apr 2002 13:09:05 +1000
From: Jeff Turner <[EMAIL PROTECTED]>
To: Log4J Users List <[EMAIL PROTECTED]>
Subject:
Under the new log4j classes, what's the equivalent of doing the following when
you need to create separate logging hiearchies:
new Hierarchy(new RootCategory(Level.DEBUG));
TIA
-- Rob
SoftSell Business Systems, Ltd.
' testing solutions for a changing world '
+44 (20) 7488 3470
www.softsell.
> Use ErrorHandler.
> It's trivial to implement.
Thanks for the suggestion - SocketAppender seems to call LogLog.error. Will this
hook into the ErrorHandler redirection, or will I need to modify the standard
SocketAppender.
TIA
- Rob
SoftSell Business Systems, Ltd.
' testing solutions for a
one enhanced/changed this area?
- Rob Walker
SoftSell Business Systems, Ltd.
' testing solutions for a changing world '
+44 (20) 7488 3470
www.softsell.com
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
Jon
Certainly be v.interested in what you find out
-- Rob
Send reply to: "Log4J Users List" <[EMAIL PROTECTED]>
Subject:RE: JDK1.4
Date sent: Mon, 18 Feb 2002 18:53:05 -
From: "Jon Skeet" <[EMAIL PROTECTED]>
To: "Log4
Not specifically Log4J related, but worthy of note.
I'd strongly suggested anyone considering moving up to JDK1.4 take a long hard
look at the following bug (and hopefully vote it up the priority list)
http://developer.java.sun.com/developer/bugParade/bugs/4523761.html
I'm lost for words how S
> What about using the XMLLayout format for the log files. This format stores
> all the information and is very easy to parse again.
>
> I wrote a simple SAX based parser for Chainsaw that does exactly this.
>
> Oliver
>
> > -Original Message-
> > From: Ro
alization and base64 encoding. I didn't bother because this hack did the
> trick for us. The base64-encoded files look like gibberish, but you can add
> another appender to the logger with some human-readable layout if you want
> to.
>
> - Heikki
>
> -Original Mes
's browsed).
It looks an easy task, but we'd also like similar facilities to the various
FileAppenders/RollingFileAppenders etc. in terms of buffered i/o and rollover.
Seems a shame to have to re-do all of this code, just to get an "unlayed-out"
object.
Anyone played with th
Up to now we've separate Hierarchies per module of our system to
allow us to have separately managed and configured loggers per
module.
It looks like Logger Repositories may offer us a more flexible
alternative, but can't quite see how their intended to be used from
the docs and examples.
Do
ons.");
> LOGGER.debug("This is a diagnostic message only meant for the
> developers.");
> }
> }
>
> log4j.rootCategory=DEBUG, A1
> log4j.appender.A1=org.apache.log4j.ConsoleAppender
> log4j.appender.A1.layout=org.apache.log4j.PatternLayout
>
> during the dev cycl
Van
We use a hybrid method:
(1) Diagnostic (i.e. developer) logging uses static Categories, with
the logging classname being use for the category name. This very
much parallels the examples in the log4j documentation. We pre-
pend all category names with "DIAG." to ease enabling/disabling of
There's probably a good reason for this, but it struck me that
InheritedThreadLocal's might help with child threads auto-inheriting
their parent's NDC.
Anyone looked into this. Immediately obvious drawback would be
compatibility, since I think ThreadLocal/InheritedThreadLocal are
JDK1.2+. But
;multiple hiearchies?
> >I've sort of got my head around what's needed from the docs, but a
> >working example would really help.
> >TIA
> >- Rob Walker
> >
> >SoftSell Business Systems, Ltd.
> >' testing solutions for a changing world &#x
This is probably an old chestnut, so I'll be brief.
Does anyone have a simple example of config'ing and using
multiple hiearchies?
I've sort of got my head around what's needed from the docs, but a
working example would really help.
TIA
- Rob Walker
SoftSell Business Sys
Thanks Ceki
- Rob
SoftSell Business Systems, Ltd.
' testing solutions for a changing world '
+44 (20) 7488 3470
www.softsell.com
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [E
Ceki,
>
> What Paul described is certainly true for the newest code in our
CVS rep. As far as I know, 1.1b1 or any previous version the
PatternLayout does time stamping when formatting the event, not
when the event was created. This was a silly bug that has been
corrected in the code in our
Ralf
We chose not to got the wrapper route.
After investigation we decided it was unlikely to improve
performance or encapsulation, and would almost certainly result in
larger code changes rather than smaller ones.
So afraid I can't help on experiences of writing log4j wrappers.
-- Rob
Paul
> I'm work on an application that logs across timezones. The timestamp I
> see in the DOS box inside of PC Anywhere connecting to the remote
> machine is one hour different than the timestamp I see in a local DOS
> box being fed by a SimpleSocketServer. Since the SimpleSocketServer
> also
taken, the issue was moving timestamping closer to
> event generation, as you would prefer.
>
> It may have been on the dev list.
>
> > -Original Message-
> > From: Rob Walker [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, April 06, 2001 11:04 AM
> > To: LO
Anuj,
> When you use PatternLayout you can specify a data attribute.
It's pretty
> sweet. Check out the javadocs for PatternLayout.
> Anuj.
Thanks for this ... maybe I'm being think but I can't see any
reference to a data attribute in PatternLayout. Can you point me at
the right spot.
Just
better
> do little more explorations on my part. If you have more
> patience kindly explain.
>
> Cheers
> VPrakash.S
>
>
> Rob Walker wrote:
> >
> > We also considered this but when you look at the scope of
> > change if you want to move away:
> >
doing. We run several apps in one WebLogic server. Each
> app has it's own Category for logging. Works great.
> - Original Message -
> From: "Rob Walker" <[EMAIL PROTECTED]>
> To: "LOG4J Users Mailing List" <[EMAIL PROTECTED]>
> Sen
We also considered this but when you look at the scope of
change if you want to move away:
* 1 import statement
* create your own version of Category to implement the new
interface to your new logging package
When you look at this, moving to a different package at a later date
is a prett
As a new user I may be raising an obvious or old question here. Is
there some way log messages can be timestamped when raised
as opposed to when logged. It's not a big deal for local logging, but
when logging over slow network links the messages in local file
based logs show different timestam
27 matches
Mail list logo
