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=40246>. 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=40246 Summary: HierarchyDynamicMBean missing unregister MBean Product: Log4j Version: 1.2 Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: Other AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] (log4j-1.2.13) I'm using log4j in a WebLogic J2EE application and added an JMX interface using the existing HierarchyDynamicMBean. During and after the first registration of the MBean, everything seems to work fine. But when I unregister the MBean and register it again (because of redeploying the application), I get a stacktrace indicating that the appender MBean is already registered. As far as I understand by reading the code, the HierarchyDynamicMBean registers the logger(s) but never unregisters them. I would expected automatic unregistration of the logger(s) when I unregister the HierarchyDynamicMBean, probably somewhere in preDeregister(). Since the addLoggerMBean() returns you the object name, the calling code can perform the cleanup itself as well, but that is IMHO not the option to prefer. In case you want to stick to this behaviour, the method needs at least some explicit javadoc comment explaining it. If someone gives a hint which direction is the best, I'm willing to write a small patch. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
