logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26435] - Changing logger priority via JMX
Date Mon, 05 Sep 2005 02:47:22 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=26435>.
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


Mime
View raw message