[LOG4J2-530] JMX Client GUI should dynamically update when LoggerContext MBeans are registered/unregistered in MBean server

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta9, 2.0-rc1
• Fix Version/s: 2.0-rc1
• Component/s: JMX
• Assignee: Remko Popma
• Reporter: Remko Popma
• Created: 07/Feb/14 09:10
• Updated: 07/Feb/14 17:50
• Resolved: 07/Feb/14 17:50

Description

Currently the Log4J2 JMX Client GUI will take a snapshot of the MBean server state when the client GUI is started. The GUI displays a tab for each LoggerContextAdmin MBean that existed at startup time.

This is a static snapshot: these tabs do not change if the LoggerContext MBean is unregistered while the GUI is active. Also, if additional LoggerContext MBeans are registered after the GUI was started, the GUI will not be "aware" of this and will not display new tabs for the added LoggerContext.

This ticket is a request to dynamically update the GUI in response to LoggerContext MBeans being registered/unregistered after the GUI was started.

• newly added LoggerContexts should result in a new tab being added for each new LoggerContext
• if MBeans for a LoggerContext are unregistered from the server, the corresponding tab should be removed from the GUI

Issue Links

• is related to: LOG4J2-500 Unloading one webapp unloads JMX MBeans for all webapps