From log4j-dev-return-11121-apmail-logging-log4j-dev-archive=logging.apache.org@logging.apache.org Mon Sep 05 02:47:25 2005 Return-Path: Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: (qmail 86540 invoked from network); 5 Sep 2005 02:47:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Sep 2005 02:47:25 -0000 Received: (qmail 21429 invoked by uid 500); 5 Sep 2005 02:47:24 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 21403 invoked by uid 500); 5 Sep 2005 02:47:24 -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 21389 invoked by uid 500); 5 Sep 2005 02:47:24 -0000 Received: (qmail 21385 invoked by uid 99); 5 Sep 2005 02:47:23 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Sep 2005 19:47:23 -0700 Received: by ajax.apache.org (Postfix, from userid 99) id 9BCAB340; Mon, 5 Sep 2005 04:47:22 +0200 (CEST) From: bugzilla@apache.org To: log4j-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 26435] - Changing logger priority via JMX X-Bugzilla-Reason: AssignedTo Message-Id: <20050905024722.9BCAB340@ajax.apache.org> Date: Mon, 5 Sep 2005 04:47:22 +0200 (CEST) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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=26435 ------- Additional Comments From jessh@ptc.com 2005-09-05 04:47 ------- There are other issues with the log4j JMX MBeans. The biggest is that a single LoggerRepository is deeply and thoroughly assumed throughout the code. If you have a LoggerRepository per web app and/or other private repositories, the log4j MBeans are useless. They also fail to disable getAttribute on password attributes. On the other hand, I believe what you're trying to do worked fine one you register the logger in question with the MBeans. I don't know for sure as I wrote my own set of MBeans some time back that now cover a good deal more than those provided with log4j. -- 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