Thanks for the reference to the JMX patch, Ceki. WebLogic 6.1 uses JMX 1.0, so I think we will not run into that JMX 1.2 issue for a while, but it's good to know.
Also, an update to my message before - I've since been able to use the Log4J MBeans to create new Appenders, and change the output file for an existing FileAppender. A key part I think I was missing before is that the activateOptions operation must be invoked on the Appender MBean before the Appender will start logging, whether it's a new Appender, or an Appender whose file has changed. As soon as you invoke activateOptions, you'll get an empty output file created, and further messages will be logged to it. Jim Ceki wrote: > Thanks for your message. There are many improvements that can be > applied to log4j's JMX support. I intend to bring many > improvements in the near future. > You might want to apply the following patch that corrects a > problem with log4j's current implementation of JMX support. > <http://marc.theaimsgroup.com/?l=log4j-dev&m=105412197117040&w=2> > I have not tried it but it makes sense. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
