[
https://issues.apache.org/jira/browse/KAFKA-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084229#comment-13084229
]
Jay Kreps commented on KAFKA-78:
--------------------------------
Shouldn't the mx4j port come from kafka config, why make it a system property?
What happens if two kafka servers are instantiated in the same jvm? We do this
for testing quite a lot.
We should also have a config to disable this feature.
> 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
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
