An error, is an error. The difference is what you do about it, not what level it's logged at.<br> (*Chris*)<br><br><div class="gmail_quote">On Sun, Aug 14, 2011 at 5:55 PM, Jason Berk <span dir="ltr"><<a href="mailto:jasonrberk@gmail.com">jasonrberk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">+1<br>
<br>
I have the exact same question<br>
<br>
Sent from my iPhone<br>
<div><div></div><div class="h5"><br>
On Aug 14, 2011, at 7:14 PM, Leon Rosenberg <<a href="mailto:rosenberg.leon@gmail.com">rosenberg.leon@gmail.com</a>> wrote:<br>
<br>
> Hi,<br>
><br>
> since logback doesn't support log level FATAL I'm wondering how you<br>
> guys are separating between 'normal' errors and 'really bad' errors.<br>
> Example:<br>
> Warning: tried to insert statement into db, found key conflict,<br>
> resolved it (somehow).<br>
> Normal errors: couldn't insert the statement into db because the<br>
> encoding is invalid (or couldn't read user's file because its corrupt)<br>
> - affects one user.<br>
> Really bad errors: have no connection to db, so my further existence<br>
> is rather meaningless.<br>
><br>
> So how do you guys log fatal errors without fatal? .-)<br>
><br>
> best regards<br>
> Leon<br>
> _______________________________________________<br>
> Logback-user mailing list<br>
> <a href="mailto:Logback-user@qos.ch">Logback-user@qos.ch</a><br>
> <a href="http://qos.ch/mailman/listinfo/logback-user" target="_blank">http://qos.ch/mailman/listinfo/logback-user</a><br>
_______________________________________________<br>
Logback-user mailing list<br>
<a href="mailto:Logback-user@qos.ch">Logback-user@qos.ch</a><br>
<a href="http://qos.ch/mailman/listinfo/logback-user" target="_blank">http://qos.ch/mailman/listinfo/logback-user</a><br>
</div></div></blockquote></div><br>