Go to the mailing list archives (theAimsGroup.com is the best) and search
for the thread with the subject of "Capturing System.err"
-Jim Moore
"I think so, Brain; but if we gave peas a chance, won't the lima beans get
jealous?" - Pinky
-----Original Message-----
From: Joseph Panico [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 12, 2001 4:43 PM
To: [EMAIL PROTECTED]
Subject: diverting System.stderr/stdout into log4j
Folks,
We use a number of third-party packages that do stderr.print... at various
random places in their code. I'm finding it quite useful to divert these
messages into our log4j heirarchy. I do this by replacing stderr/stdout with
my own PrintStreams that log the lines to a special log4j Category-- as
suggested on this list a while back. The only fly-in-the-ointment with this
scheme is LogLog. If there is a problem with log4j such that it cannot log
for some reason, then log4j internals use LogLog to attempt to print an
error message. This obviously leads to an infinite recursion. Has anyone
else been bothered by this? Would it make sense to add interface to LogLog
which would set the PrintStream it uses to log its error messages to?
thanks for any ideas
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
