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=23021>. 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=23021 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|[email protected]|[email protected] ------- Additional Comments From [EMAIL PROTECTED] 2005-07-22 01:59 ------- I'm a little troubled by the proposed resolution. An Appender should not throw a run-time exception and the exception would not be caught if the appender was directly attached to the logger hierarchy. I'd really prefer not to suggest that an appender that throws run-time exceptions is tolerable as long as you wrap it in an async appender. I'm not sure of the cost of the try/catch block in the async appender for the run-time exception that should never come, but it could be expensive enough to be noticable. My current preference is to check dispatcher.isAlive() at the start of AsyncAppender.doAppend and if the dispatch thread has died to invoke the nested appenders synchronously. This should result in similar behavior for both the sync and async other than your first exception is silent if wrapped in an async appender. -- 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]
