incubator-kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Burroughs (Updated) (JIRA)" <>
Subject [jira] [Updated] (KAFKA-78) add optional mx4j support to expose jmx over http
Date Tue, 04 Oct 2011 02:06:34 GMT


Chris Burroughs updated KAFKA-78:

    Attachment: k78-v3.txt

Sorry for the delay.

 - License header format updated.
 - Added -Dmx4jdisable to disable mx4j even if it's on the classpath.

They are system properties because it only makes sense to have one mx4j port per JVM (like
jmx ports), not one per embedded broker.  If there is a case there you have a lot of embedded
brokers, and mx4j (ie not a test), and the log messages are annoying I can add some more complicated
"do only once" code.

Unit tests should be unaffected since we don't have a hard dep on mx4j.
> add optional mx4j support to expose jmx over http
> -------------------------------------------------
>                 Key: KAFKA-78
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message