[
https://issues.apache.org/jira/browse/FLUME-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219005#comment-14219005
]
Hudson commented on FLUME-1594:
-------------------------------
SUCCESS: Integrated in Flume-trunk-hbase-98 #55 (See
[https://builds.apache.org/job/Flume-trunk-hbase-98/55/])
FLUME-1594. Document JMX options (roshan:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=35de8ff18d096bd41caf3dabbcadc70b7d90ac40)
* flume-ng-doc/sphinx/FlumeUserGuide.rst
> Document JMX options
> --------------------
>
> Key: FLUME-1594
> URL: https://issues.apache.org/jira/browse/FLUME-1594
> Project: Flume
> Issue Type: Documentation
> Components: Configuration
> Affects Versions: v1.3.0, v1.4.0
> Reporter: Will McQueen
> Assignee: Ashish Paliwal
> Fix For: v1.6.0
>
> Attachments: FLUME-1594-0.patch
>
>
> We should add to the Flume User Guide a section on how to enable JMX, and a
> sample using JConsole. We can reference this link in the docs too:
>
> http://docs.oracle.com/javase/6/docs/technotes/guides/management/agent.html
> The following sample JVM args (set in flume-env.sh) allow me to successfully
> use JConsole to monitor a remove Flume agent:
> JAVA_OPTS="-Xms1024m -Xmx1024m -Dcom.sun.management.jmxremote
> -Dcom.sun.management.jmxremote.port=5445
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
