You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2005/10/17 16:29:08 UTC
DO NOT REPLY [Bug 37122] New: -
Issue upgrading JBoss to log4j 1.2.12
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37122>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37122
Summary: Issue upgrading JBoss to log4j 1.2.12
Product: Log4j
Version: 1.2
Platform: All
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Appender
AssignedTo: log4j-dev@logging.apache.org
ReportedBy: jasper_rosenberg@yahoo.com
JBoss's Log4jService loads the log4j.xml file, and then overwrites
System.err/System.out to redirect to log4j.
This used to work before 1.2.12 because the ConsoleAppender would always use the
stream with which it was initialized. Unfortunately, with the fix of bug 31056
this trick no longer works, and an infinite loop is created.
This seems like reasonable behavior to support, wanting to use the
ConsoleAppender, but also wanting to redirect all System.out/err to the logging
system.
Perhaps a boolean flag can be added to ConsoleAppender such as "cacheTarget", so
that in activateOptions() it behaves like 1.2.11 if cacheTarget is true, and
1.2.12 if cacheTarget is false.
Thanks,
Jasper
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org