[
https://issues.apache.org/jira/browse/KAFKA-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120318#comment-13120318
]
Jun Rao commented on KAFKA-78:
------------------------------
Chris, thanks for the patch. Do you think that we can change mx4jdisable to
mx4jenable so that if the user doesn't specify the property, the mx4j part is
not touched? This way, users who already use mx4j but don't want mx4j to be
loaded in the embedded Kafka broker are not affected by default.
> add optional mx4j support to expose jmx over http
> -------------------------------------------------
>
> Key: KAFKA-78
> URL: https://issues.apache.org/jira/browse/KAFKA-78
> Project: Kafka
> Issue Type: New Feature
> Reporter: Chris Burroughs
> Assignee: Chris Burroughs
> Priority: Minor
> Fix For: 0.7
>
> Attachments: k78-v1.txt, k78-v2.txt, k78-v3.txt
>
>
> In the fun world of operations and monitoring sometimes HTTP is a better
> choice than 'real' jmx for alerting. mx4j exposes jmx beans over HTTP (sadly
> with xml). Attached patch is a scala port of CASSANDRA-1068 that optionally
> loads mx4j if it is present on the classpath.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
