📄 mail-2001-03-12t1326
字号:
Copied from:http://www.mail-archive.com/log4j-user@jakarta.apache.org/msg00430.html--------------------------------------------------------------------------------diverting System.stderr/stdout into log4j--------------------------------------------------------------------------------From: Joseph Panico Subject: diverting System.stderr/stdout into log4j Date: Mon, 12 Mar 2001 13:26:41 -0800 --------------------------------------------------------------------------------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 ideasjoe_________________________________________________________________Get your FREE download of MSN Explorer at http://explorer.msn.com---------------------------------------------------------------------To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.orgFor additional commands, e-mail: log4j-user-help@jakarta.apache.org
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -