Return-Path: Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: (qmail 31950 invoked from network); 28 Jan 2008 14:18:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Jan 2008 14:18:21 -0000 Received: (qmail 11643 invoked by uid 500); 28 Jan 2008 14:18:10 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 11611 invoked by uid 500); 28 Jan 2008 14:18:10 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 11600 invoked by uid 99); 28 Jan 2008 14:18:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2008 06:18:10 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2008 14:18:04 +0000 Received: by brutus.apache.org (Postfix, from userid 33) id 649F9714233; Mon, 28 Jan 2008 06:17:56 -0800 (PST) From: bugzilla@apache.org To: log4j-dev@logging.apache.org Subject: DO NOT REPLY [Bug 44308] New: - [Patch] JMX component for managing Logger configurations Message-ID: X-Bugzilla-Reason: AssignedTo Date: Mon, 28 Jan 2008 06:17:56 -0800 (PST) X-Virus-Checked: Checked by ClamAV on apache.org DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=44308 Summary: [Patch] JMX component for managing Logger configurations Product: Log4j Version: 1.2 Platform: All OS/Version: All Status: NEW Keywords: PatchAvailable Severity: enhancement Priority: P2 Component: Other AssignedTo: log4j-dev@logging.apache.org ReportedBy: stefan.fleiter@web.de Log4j comes with HierarchyDynamicMBean for managing Log4j by means of JMX. This class has the following restrictions: - It can not be registered more than once at the same MBean server, this is a critical restriction in J2EE Environments. - Only loggers specified in the Log4j configuration file can be configured. - The code is overly complex. Since these restrictions are by design I have implemented a more straight forward solution to this problem. LoggerManager: Class with Methods for managing loggers LoggerManagerModelMBean: Model MBean which makes LoggerManager methods available per JMX RollbackableLoggerManager: Extension to LoggerManager which records intial state for all changed loggers and offers a method to roll them back -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org