Ok, more information: The application is a servlet running in Tomcat. I thought it would be a nice "feature" for the administrator of the application to be able to go in and change the logging level for the servlet on the fly. Unfortunately, the first thing they did is change it from INFO to DUBUG (instead of DEBUG). They didn't notice the error and I started getting strange behavior, like the same line being logged multiple times and other output not being logged at all.
So I guess what I was asking was if there was any way for the servlet to defend itself from these typos? Maybe it could catch a parsing error thrown by PropertyConfigurator and then log an error message saying they misconfigured the logger. It is an option for me to just tell them to be more careful, but I am investigating alternatives. Thanks, B ----- Original Message ----- From: "Ylan Segal" <[EMAIL PROTECTED]> To: "Log4J Users List" <[EMAIL PROTECTED]> Sent: Friday, March 15, 2002 5:01 PM Subject: RE: improperly specified logging level > Brian, > > > The unexpected behavior varies depending on if the typo was > > introduced while > > Log4J was already running or if it was already there when > > Log4J is initialized. In either case, I'd like to defend against > > this type > > of error. Any ideas? > > I don't think I understand. What do you want log4j to do with the typos? > Where is the typo? And more importantly, if you know the problem is a typo, > why do you just fix it and be done with it? > > Ylan Segal. > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
