Nick, Will you be making these changes?
Gary On Tue, Jul 16, 2013 at 12:39 PM, Ralph Goers <[email protected]>wrote: > As a general rule exceptions in appenders that cause the log event to fail > to be written should be percolated. AppenderControl has the ability to > suppress them if that is what the user wants. But the FailoverAppender > can't do its work unless the exceptions percolate to it. > > Ralph > > On Jul 16, 2013, at 8:52 AM, Nicholas Williams wrote: > > > If it helps, check out LOG4J2-291. I may be handling errors > > incorrectly in the JDBC/JPA/NoSQL appenders. If an exception is thrown > > within the *Manager write methods, should I just let that exception > > propagate (wrapping it if it's a checked exception that I can't > > throw)? Should I wrap all exceptions in some standard exception > > (LoggingException or something similar)? Right now I'm catching > > exceptions and logging them using the SimpleLogger. I may need to > > change that behavior. > > > > Nick > > > > --------------------------------------------------------------------- > > 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] > > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
