[
https://issues.apache.org/jira/browse/FLUME-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459252#comment-13459252
]
Hari Shreedharan commented on FLUME-1594:
-----------------------------------------
{code} -Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false {code}
This will disable security on the jmx remote monitoring and leave a port open
on the machine. We must also document the security risk involved. There are
ways to keep the port secure, which is documented in the link you posted in the
description.
> Document JMX options
> --------------------
>
> Key: FLUME-1594
> URL: https://issues.apache.org/jira/browse/FLUME-1594
> Project: Flume
> Issue Type: Bug
> Components: Configuration
> Affects Versions: v1.3.0
> Reporter: Will McQueen
> Fix For: v1.3.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
