[ http://jira.qos.ch/browse/LBCLASSIC-114?page=com.atlassian.jira.plugin.syste... ] Philippe Marschall updated LBCLASSIC-114: ----------------------------------------- Attachment: (was: JmxEnabler.java)

add a context listener that automatically configures JMX --------------------------------------------------------

Key: LBCLASSIC-114 URL: http://jira.qos.ch/browse/LBCLASSIC-114 Project: logback-classic Issue Type: New Feature Components: Other Reporter: Philippe Marschall Assignee: Logback dev list Priority: Minor Attachments: JmxEnabler.java

Setting up logback JMX for a web application requires a bit too many manual steps. It is not enough to simply add <jmxConfigurator /> to the configuration file. You should also set the context path but often you can't know that in advance. In addition you still need to write custom code to [prevent memory leaks|http://logback.qos.ch/manual/jmxConfig.html#leak]. These issues could all be addressed by a custom context listener. <listener> <listener-class>ch.qos.logback.classic.selector.servlet.JmxEnabler</listener-class> </listener> Code attached.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.qos.ch/browse/LBCLASSIC-114?page=com.atlassian.jira.plugin.syste... ] Paul Nyheim commented on LBCLASSIC-114: --------------------------------------- The suggested implementation uses ServletContext.getContextPath, which was introduced in servlet-api 2.5 which makes it unusable on any J2EE 1.4 compatible app-server (such as WebSphere 6.1). While logback has a dependency on servlet-api 2.5, it is still compatible with servlet-api 2.4 AFAIK.

add a context listener that automatically configures JMX --------------------------------------------------------

Key: LBCLASSIC-114 URL: http://jira.qos.ch/browse/LBCLASSIC-114 Project: logback-classic Issue Type: New Feature Components: Other Reporter: Philippe Marschall Assignee: Ceki Gulcu Priority: Minor Attachments: JmxEnabler.java

Setting up logback JMX for a web application requires a bit too many manual steps. It is not enough to simply add <jmxConfigurator /> to the configuration file. You should also set the context path but often you can't know that in advance. In addition you still need to write custom code to [prevent memory leaks|http://logback.qos.ch/manual/jmxConfig.html#leak]. These issues could all be addressed by a custom context listener. <listener> <listener-class>ch.qos.logback.classic.selector.servlet.JmxEnabler</listener-class> </listener> Code attached.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira