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=40382>. 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=40382 ------- Additional Comments From [EMAIL PROTECTED] 2006-09-01 17:14 ------- SyslogAppender in log4j is implemented as a pure Java class using network IO (even when logging to localhost) and does not call the ::syslog native method. The implementation has the advantage of being platform independent, but will not work if syslogd is not accepting network connections or if the security manager prevents the creation of sockets. There is a enhancement request for a JNI implementation of SyslogAppender (http://issues.apache.org/bugzilla/show_bug.cgi?id=27363) along with an implementation. It is likely that you are running into one of the blockers mentioned (at least in the start up phase). How that affect system booting is unclear. I'm guessing that if you change your config file to use another appender (for example, ConsoleAppender), then you start up process would work fine. The exception thrown when trying to connect to syslogd seems to be caught properly, but perhaps instead of subsequent log requests failing, they block somehow. I've reviewed both the log4j 1.2 and 1.3 implementations and don't see a mechanism for logging after the observed warning to cause a lock up. this.ds should be null and the write methods in SyslogWriter do check that and though they unnecessary create DatagramPackets, they do not attempt to send them. The code could be optimized by avoiding short-circuiting the write statements if this.ds == null. Perhaps the lock up is due to something else in the app and is not related to the SyslogAppender. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
