[jboss-jira] [JBoss JIRA] Moved: (LOGMGR-31) The JMX Bean associated with a LogContext must be made available

David Lloyd (JIRA) jira-events at lists.jboss.org
Fri Sep 23 10:00:27 EDT 2011


     [ https://issues.jboss.org/browse/LOGMGR-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Lloyd moved JBLOGGING-71 to LOGMGR-31:
--------------------------------------------

    Project: JBoss Log Manager  (was: JBoss Logging)
        Key: LOGMGR-31  (was: JBLOGGING-71)


> The JMX Bean associated with a LogContext must be made available
> ----------------------------------------------------------------
>
>                 Key: LOGMGR-31
>                 URL: https://issues.jboss.org/browse/LOGMGR-31
>             Project: JBoss Log Manager
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>         Environment: JBoss AS 6.0.0
>            Reporter: Leonid Kosmylev
>            Assignee: David Lloyd
>
> Class org.jboss.logmanager.LogContext has an associated instance of LoggingMXBeanImpl. If per-application logging is enabled a new instances of LogContext and  LoggingMXBeanImpl are created. But the LoggingMXBeanImpl is not registered as an MBean. It is therefore not possible to change log levels dynamically.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list