Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Received-SPF: pass (athena.apache.org: domain of will.sargent@gmail.com
 designates 209.85.146.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=kiUoGjcCWLZQIxRjoZf72hpTnJ9AyaFslCMPo911bZyZ/TfsdQeWxmw1ZwrJqtFFJksXZuQSPx84c/qkPWmdxwkVqI4bni5wTfKrfyTNpckYh/AoD2yWLqS4ZDeRSWnuYuAymAI+zLjBe5yzNeDvA/PmNPcR+A+9WRurfQsPFc8=
Message-ID: <b2a849dd0710251844r147afc9eu21b3d5e0ded251ec@mail.gmail.com>
Date: Thu, 25 Oct 2007 18:44:02 -0700
From: "Will Sargent" <will.sargent@gmail.com>
To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Subject: Re: Changing logging levels in Log4J dynamically?
In-Reply-To: <472143B7.90403@ptc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <b2a849dd0710251437k505b53aci1cc291c72c7b5f5@mail.gmail.com>
	 <472143B7.90403@ptc.com>

I've researched this in the past, and I did find a number of examples
of people using JMX with log4j.  So it's doable.

http://blogs.averconsulting.com/2006/12/13/changing-log4j-logging-levels-dynamically.aspx

http://www.devx.com/Java/Article/32359/1954?pf=true

http://technology.amis.nl/blog/?p=1238

If the JMX code in 1.2.14 is not usable on its own, what does it do?
Is it a starting point?

Will.

On 10/25/07, Jess Holle <jessh@ptc.com> wrote:
> Though I believe there have been recent fixes to it, I ended up giving
> up on the JMX package in log4j and writing my own.
>
> You may be able to make it work well enough for your cases if you only
> have a single LoggerRepository, though.  If not, well last I saw it had
> no notion or ability to cope with multiple repositories and I'd suggest
> using the code as an sample code for writing your own at that point --
> taking what you like and leaving the rest :-)
>
> As for documentation, I'd suggest running with Java 5, adding the bit of
> code to register the MBeans, connecting to your running app with
> jconsole and playing around.  You'll quickly see what's handled to your
> liking and what's not this way.
>
> Besides JMX, there's always just calling setLevel() yourself -- as
> triggered by an HTTP request, for example.  You can also watch for
> modifications to the log4j configuration file and reconfigure when it
> changes -- not instantaneous, but still no restart required.
>
> --
> Jess Holle
>
> Will Sargent wrote:
> > Hi all,
> >
> > I've heard several people ask if you can change log4j levels
> > dynamically, once the application is already running. I see that
> > there's a JMX package in 1.2.14, but there doesn't seem to be any
> > javadoc or documentation attached to it.  If there is, can someone
> > point me to it?
> >
> > Will.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org