What we now have in ServiceMix (thanks to Thomas) is something
that could be done in ActiveMQ as well. This is a small service
than you can configure and which expose a simple bean from JMX.
This mbean can be used to configure a timer and activate / deactivate
it so that the log4j configuration is reloaded. You can also manually
call an update if you have changed the configuration.
Note that this does not actually allow to change the log level using JMX,
as you still have to change the log4j configuration file.
On 4/13/07, Bruce Snyder <[EMAIL PROTECTED]> wrote:
On 4/13/07, davidmc <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
> We are interested in enhancing ActiveMQ's current logging functionality,
to
> help with debugging and profiling. This would be a contribution to
ActiveMQ
> source code.
>
> Basically we would like to add the following features at the Transport
> level:
> -Allow different, customizable logging formats. For example, the current
> format is human readable but not easily processed by a machine.
This already offered via Log4J configuration. See conf/log4j.properties.
> -Allow dynamic ON/OFF switching of logging (probably with JMX).
This isn't done currently but could easily be refactored to utilize
the Log4J DOMConfigurator.configureAndWatch() method.
Bruce
--
perl -e 'print
unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/
--
Cheers,
Guillaume Nodet
------------------------
Principal Engineer, IONA
Blog: http://gnodet.blogspot.com/