> Hi Rob, > > Log4j's initialization is invoked through static initializers. These are > not run as a result of a configuration reset. Most of my log4j experience > is restricted to Java application servers (most recently J2EE based ones). > In this case, I see people calling the LogManager's reset within a > servlet's init method in order to run a configuration from a clean slate. > The servlet is configured to run at app server startup where the concern > about blocked logging threads is minimal. > > I would be concerned about calling reset on a heavily loaded app server. > Normally I would restrict reconfigurations to simple modifications either > through JMX or through a configuration without a reset invocation. For a > running app server, by far the most common operation is ajusted log levels. > Adding or reconfiguring appenders is rare.
Good point! Thanks. Later Rob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
