-
1. Re: M1 issue - database gets corrupted.
starksm64 May 16, 2004 10:40 AM (in response to acoliver)There is a general logging level guide line here:
http://www.jboss.org/developers/guides/logging -
2. Re: M1 issue - database gets corrupted.
acoliver May 16, 2004 5:22 PM (in response to acoliver)nevermind. I fixed it. That was mind numbing. I just forgot to check in build changes so onLoad wasn't happening when I thought.
-
3. Re: M1 issue - database gets corrupted.
spiritualmechanic May 16, 2004 5:40 PM (in response to acoliver)What is your basic strategy for "rationalize our logging and error handling a bit"? That's something easy that I can do and would save you guys some time.
-
4. Re: M1 issue - database gets corrupted.
acoliver May 16, 2004 6:05 PM (in response to acoliver)Stuff that should be "error" and "warn" and "info" and so forth. Furthermore sample configurations for logging different stuff (like only pop or only smtp and maybe only what comes from the client and only from the server, etc). The latter might be best on the wiki. Just come up with a strategy and make it all consistent and make sure things that should log do.
Error handling....I think we're catching things that should propegate themselves as reasonable errors. Basically find all the try/catch blocks and figure out what should be caught, thrown and what should be propegated as a protocol error, etc. It should be both consistent and "to spec" especially in the latter case.