Hi Scott,
Please make sure that you can actually safely contribute the code. If you suspect that there might be copyright violation, it is preferable not to contribute. Thank you in advance for your understanding.
At 03:56 PM 6/18/2003 -0700, you wrote:
Howdy, Sending it to the list would be great. Putting the Apache license (you can copy and paste from any of the log4j source file) on top would be even better ;) I can commit it into the log4j-sandbox at that point. Thanks!
Yoav Shapira
--- Scott Heaberlin <[EMAIL PROTECTED]> wrote: > I probably won't be able to directly donate the code we have. But, as > the original author, I'm sure I could recreate it at home without the > company-specific code in it. > > How would you like me to submit it? To the list? I can probably have it > cranked out in a couple of days or so. I'll read up on the submissions > doc on the site and get to crackin'. > > > -Scott Heaberlin > > > > -----Original Message----- > > From: Yoav Shapira [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 17, 2003 7:24 PM > > To: Log4J Users List > > Subject: RE: Fallback Error Handler behavior > > > > > > Howdy, > > Can you share your FailoverErrorHandler for possible > > inclusion in future log4j versions? > > > > Yoav Shapira > > > > --- Scott Heaberlin <[EMAIL PROTECTED]> wrote: > > > No, we encountered similar behavior (losing the event that *caused* > > > the primary appender to call errorHandler.error(...)) and looked at > > > the source for the FallbackErrorHandler. > > > > > > Our solution was to create a new error handler class called > > > FailoverErrorHandler which never replaces the primary > > Appender. In the > > > event of its primary Appender calling any signature of > > error(...), our > > > custom error handler class simply wrote to standard out and > > sent the > > > LoggingEvent to the backup appender. (We did add some other custom > > > code to our new error handler that would report errors by > > other means > > > as well, typically by using a named Logger instance... but that's > > > another story). > > > > > > In short, the current FallbackErrorHandler implementation simply > > > "switches" Appenders for the Logger whenever *some* but not > > all of the > > > ErrorHandler::error(...) methods are called. For > > "failover" behavior > > > you'll have to implement your own custom ErrorHandler (it's > > not that > > > difficult though - one of my favorite aspects of Log4J is > > its design - > > > the simplicity of implementing/extending the Interfaces and base > > > classes to achieve exactly the functionality your > > enterprise requires. > > > > > > Hope this helps, > > > > > > > > > -Scott Heaberlin > > > > > > > > > > -----Original Message----- > > > > From: Buchanan, Paul [mailto:[EMAIL PROTECTED] > > > > Sent: Tuesday, June 17, 2003 1:46 PM > > > > To: '[EMAIL PROTECTED]' > > > > Subject: Fallback Error Handler behavior > > > > > > > > > > > > I have a few questions regarding the FallbackErrorHandler's > > > > behavior. I have a FallbackErrorHandler attached to an > > > > appender that writes to a SQL database. From my testing, it > > > > looks like upon the first error writing to the database, the > > > > FallbackErrorHandler adds the secondary appender to the > > > > logger, and the event is not logged. Log events after this > > > > are then logged to both the primary and secondary appenders > > > > regardless of the existence of an error. Upon another error, > > > > the event is correctly logged to the secondary appender. > > > > > > > > It was my understanding that each and every event would be > > > > logged, and that the secondary appender would only be logged > > > > to in event of an error. This is not the behavior that I am > > > > experiencing. Should I be getting different behavior? > > > > > > > > Thanks, > > > > > > > > Paul Buchanan > > > > email: [EMAIL PROTECTED] > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > ===== > > Yoav Shapira > > [EMAIL PROTECTED] > > > > __________________________________ > > Do you Yahoo!? > > SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
===== Yoav Shapira [EMAIL PROTECTED]
__________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Ceki For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
