You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2008/12/22 22:49:44 UTC

[jira] Commented: (ZOOKEEPER-256) support use of JMX to manage log4j configuration at runtime

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658677#action_12658677 ] 

Mahadev konar commented on ZOOKEEPER-256:
-----------------------------------------

this code change uses a property to disable jmx ("zookeeper.jmx.log4j.disable")  in log4j. Shouldnt this be documented? 

> support use of JMX to manage log4j configuration at runtime
> -----------------------------------------------------------
>
>                 Key: ZOOKEEPER-256
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-256
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: jmx
>            Reporter: Patrick Hunt
>            Assignee: Patrick Hunt
>             Fix For: 3.1.0
>
>         Attachments: ZOOKEEPER-256.patch
>
>
> Log4j has code to support management at runtime using JMX. Need to add hooks to register the beans.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.