You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "FOSTER, Andrew" <An...@london.sema.slb.com> on 2003/06/09 16:42:30 UTC
Reconfiguring log4J in an AppServer at runtime
Hi,
We are using log4J to implement our logging strategy on our AppServer.
The settings are configured using the log4J.properties file that is found
during log4Js default initialisation sequence. On production all settings
will be set to the error level. If you wish to change this then the
appServer will need to be restarted in a controlled manner to pick up the
new file during initialisation.
Is there a recommended way to set up log4J so you can change the levels at
runtime and the code automatically picks this up. Obviously a way that does
not break the EJB spec and ensures all instances of log4J get updated for
each classloader.
regards
Andy Foster
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
Re: Reconfiguring log4J in an AppServer at runtime
Posted by Jacob Kjome <ho...@visi.com>.
In the log4j-sandbox project there is a ConfigurationServlet which can
modify loggers at runtime. There are also a couple other projects outside
of log4j:
http://isavix.net/codeexchange/codeexchange-viewdetail.jsp?id=136
and
http://www.codeczar.com/projects/logweb/
Hope that helps.
Jake
At 06:38 AM 6/11/2003 -0400, you wrote:
>You should be able to do that through the JMX interface.
>
>Bill
>
>On Mon, 9 Jun 2003, FOSTER, Andrew wrote:
>
> > Hi,
> >
> > We are using log4J to implement our logging strategy on our AppServer.
> >
> > The settings are configured using the log4J.properties file that is found
> > during log4Js default initialisation sequence. On production all settings
> > will be set to the error level. If you wish to change this then the
> > appServer will need to be restarted in a controlled manner to pick up the
> > new file during initialisation.
> >
> > Is there a recommended way to set up log4J so you can change the levels at
> > runtime and the code automatically picks this up. Obviously a way that does
> > not break the EJB spec and ensures all instances of log4J get updated for
> > each classloader.
> >
> > regards
> >
> > Andy Foster
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
> >
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
Re: Reconfiguring log4J in an AppServer at runtime
Posted by Bill Rossi <bi...@rossi.com>.
You should be able to do that through the JMX interface.
Bill
On Mon, 9 Jun 2003, FOSTER, Andrew wrote:
> Hi,
>
> We are using log4J to implement our logging strategy on our AppServer.
>
> The settings are configured using the log4J.properties file that is found
> during log4Js default initialisation sequence. On production all settings
> will be set to the error level. If you wish to change this then the
> appServer will need to be restarted in a controlled manner to pick up the
> new file during initialisation.
>
> Is there a recommended way to set up log4J so you can change the levels at
> runtime and the code automatically picks this up. Obviously a way that does
> not break the EJB spec and ensures all instances of log4J get updated for
> each classloader.
>
> regards
>
> Andy Foster
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org