-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adam,
Adam Gordon wrote: > Wow, no one had any ideas as to what is going on? I have no idea if Tomcat supports this -- the logging-related configuration directives in the docs should say if it is directly supported. If you're using log4j, I know that there are tools you can use to modify the in-memory configuration of the logging framework, but they won't be persisted to the disk (and they don't allow you re-read the configuration file AFAIK). > Anyway. We never figured out why Tomcat has an issue with this, but we > found a suitable workaround by basically doing what the LogHandler does > when it re-reads and refreshes the logging configuration - we take the > new logging level values and apply them to their respective loggers. Where do you do this? In your webapp or somewhere else? > In fact, my first test was an exact copy of the LogHandler code and the > test worked (i.e., dynamic logging worked), whereas using the LogHandler > didn't....hmmmm. If you come up with something, consider logging a bug/enhancement and submitting a patch. Suggestions with patches are usually given higher priority than those without patches ;) - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHDm2x9CaO5/Lv0PARAhWXAJ4nVi21oqN7A99wtoZMtY1HzfUQNwCcDR8Q ivOydqjYdN1xGwtd1WqrU8c= =4Bp9 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
