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/08/05 01:05:47 UTC
DO NOT REPLY [Bug 35743] -
SyslogAppender throws a NullPointerException upon misconfiguration
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=35743>.
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=35743
------- Additional Comments From mthornton@swri.org 2005-08-05 01:05 -------
I just thought logging a warning at configuration time as when there are no
appenders found would be appropriate. Your average log4j user, given a
warning that the syslog host did not exist or something to that effect, could
then track down the problem, and the application wouldn't explode because the
logging was misconfigured.
I'm pretty sure that a logging tool should never throw errors back to an
application. Logging is almost never mission-critical. I suppose someone
could debate the point, but I think most people would agree.
--
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