Return-Path: 
 <log4j-user-return-19339-apmail-logging-log4j-user-archive=logging.apache.org@logging.apache.org>
Delivered-To: apmail-logging-log4j-user-archive@www.apache.org
Received: (qmail 59213 invoked from network); 17 Nov 2006 15:22:03 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 17 Nov 2006 15:22:03 -0000
Received: (qmail 22210 invoked by uid 500); 17 Nov 2006 15:22:03 -0000
Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org
Received: (qmail 22170 invoked by uid 500); 17 Nov 2006 15:22:03 -0000
Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:log4j-user-unsubscribe@logging.apache.org>
List-Help: <mailto:log4j-user-help@logging.apache.org>
List-Post: <mailto:log4j-user@logging.apache.org>
List-Id: "Log4J Users List" <log4j-user.logging.apache.org>
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
Delivered-To: mailing list log4j-user@logging.apache.org
Received: (qmail 22149 invoked by uid 99); 17 Nov 2006 15:22:03 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Nov 2006 07:22:03 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of nicolas.deloof@capgemini.com
 designates 194.3.247.82 as permitted sender)
Received: from [194.3.247.82] (HELO mxepar01.capgemini.com) (194.3.247.82)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Nov 2006 07:21:49 -0800
Received: from mxipar01.capgemini.com (prvmta2 [194.3.224.82])
	by mxepar01.capgemini.com (8.13.6/8.13.6) with ESMTP id kAHFLOhs004093
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <log4j-user@logging.apache.org>; Fri, 17 Nov 2006 16:21:26 +0100 (MET)
Received: from prvmta2.capgemini.com (localhost [127.0.0.1])
	by mxipar01.capgemini.com (8.13.6/8.13.6) with ESMTP id kAHFLNJi007906
	for <log4j-user@logging.apache.org>; Fri, 17 Nov 2006 16:21:23 +0100 (MET)
Received: from pasteur2.capgemini.fr (smtp.capgemini.fr [10.67.1.90])
	by prvmta2.capgemini.com (8.13.6/8.13.6) with ESMTP id kAHFLMRl007886
	for <log4j-user@logging.apache.org>; Fri, 17 Nov 2006 16:21:22 +0100 (MET)
Received: from pasteur.capgemini.fr (localhost [127.0.0.1])
	by pasteur2.capgemini.fr (8.12.10/8.12.10) with ESMTP id kAHFLMTG022159
	for <log4j-user@logging.apache.org>; Fri, 17 Nov 2006 16:21:22 +0100 (MET)
Received: from [10.67.188.137] ([10.67.188.137])
	by pasteur.capgemini.fr (8.12.10/8.12.10) with ESMTP id kAHFLKeS022074
	for <log4j-user@logging.apache.org>; Fri, 17 Nov 2006 16:21:20 +0100 (MET)
Message-ID: <455DD370.40309@capgemini.com>
Date: Fri, 17 Nov 2006 16:21:20 +0100
From: Nicolas DE LOOF <nicolas.deloof@capgemini.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Log4J Users List <log4j-user@logging.apache.org>
Subject: Re: Access Log4J with JMX ?
References: <41401bff0611170640g272b0f04gcf03bf17847a4906@mail.gmail.com>
In-Reply-To: <41401bff0611170640g272b0f04gcf03bf17847a4906@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked by ClamAV on apache.org


I'm using it via Spring jmx this way :

    <bean id="mbeanExporter"
        class="org.springframework.jmx.export.MBeanExporter">
        <property name="beans">
            <map>
                <entry key="log4j:hiearchy=default">
                    <bean 
class="org.apache.log4j.jmx.HierarchyDynamicMBean"/>
                </entry>
            </map>
        </property>
        <property name="server" ref="mbeanServer"/>
    </bean>

This gives me acces to the log4j MBeans to get existing loggers and 
change levels. Please note I can ONLY get MBeans for existing loggers, 
so I have to define categories in log4j.xml for every logger in my app 
that I'd like to configure at runtime.

Maybe next log4j versions will allow a finer JMX management.

Nico.

gaspode a �crit :
> Hi all,
>
> I'd like to change the Log4J configuration remotely while my app is 
> running.
> I started a simple JMX solution when I noticed that Log4J already 
> includes a
> JMX package : org.apache.log4j.jmx.
>
> Unfortunately, this package is not well documented, and I could not 
> find any
> mention of it in "The Complete Log4J Manual" (Ceki G�lc�) that I recently
> bought.
>
> Could somebody explain me how to use it or point me to some online doc?
>
> I understand that LoggerDynamicMBean, LayoutDynamicMBean and
> LoggerDynamicMBean are all wrapper around a Logger, a Layout or an 
> Appender.
> But most of my apps use lots of Loggers, Appenders,... do I have to 
> publish
> a MBean for each of them? Isn't that a bit awkward? If I access them with
> jconsole I will end up with lot's of hard to read info. Or is there a 
> Log4J
> JMX GUI client somewhere that present me all that in a friendly way? 
> Or do I
> have to create one? (and if so, is anybody interrested in joining the
> project ? :-> ).
>
> Cheers all,
>
> me.
>

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.


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