You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Flavio Paiva Junqueira (JIRA)" <ji...@apache.org> on 2009/01/15 15:59:02 UTC
[jira] Created: (ZOOKEEPER-274) Document options to connect
Jconsole remotely
Document options to connect Jconsole remotely
---------------------------------------------
Key: ZOOKEEPER-274
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-274
Project: Zookeeper
Issue Type: Improvement
Reporter: Flavio Paiva Junqueira
Priority: Minor
Here is the command I used:
java -cp .:./zookeeper-dev.jar:/usr/local/apache-log4j-1.2.15/log4j-1.2.15.jar -Dlog4j.configuration=log4j_console.properties -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=12122 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false org.apache.zookeeper.server.quorum.QuorumPeerMain zoo.cfg
In addition to the ones in jira 234, we also need the following to connect remotely:
-Dcom.sun.management.jmxremote.port
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
This command assumes no authentication or secure connection through ssl. To use authentication, other options are necessary, such as the password file:
-Dcom.sun.management.jmxremote.password.file
In general, I found the following page a good source of information on this topic:
http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-274) Document options to connect
Jconsole remotely
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-274:
-----------------------------------
Fix Version/s: 3.2.0
> Document options to connect Jconsole remotely
> ---------------------------------------------
>
> Key: ZOOKEEPER-274
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-274
> Project: Zookeeper
> Issue Type: Improvement
> Components: jmx
> Reporter: Flavio Paiva Junqueira
> Priority: Minor
> Fix For: 3.2.0
>
>
> Here is the command I used:
> java -cp .:./zookeeper-dev.jar:/usr/local/apache-log4j-1.2.15/log4j-1.2.15.jar -Dlog4j.configuration=log4j_console.properties -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=12122 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false org.apache.zookeeper.server.quorum.QuorumPeerMain zoo.cfg
> In addition to the ones in jira 234, we also need the following to connect remotely:
> -Dcom.sun.management.jmxremote.port
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false
> This command assumes no authentication or secure connection through ssl. To use authentication, other options are necessary, such as the password file:
> -Dcom.sun.management.jmxremote.password.file
> In general, I found the following page a good source of information on this topic:
> http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-274) Document options to connect
Jconsole remotely
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt reassigned ZOOKEEPER-274:
--------------------------------------
Assignee: Patrick Hunt
> Document options to connect Jconsole remotely
> ---------------------------------------------
>
> Key: ZOOKEEPER-274
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-274
> Project: Zookeeper
> Issue Type: Improvement
> Components: jmx
> Reporter: Flavio Paiva Junqueira
> Assignee: Patrick Hunt
> Priority: Minor
> Fix For: 3.2.0
>
>
> Here is the command I used:
> java -cp .:./zookeeper-dev.jar:/usr/local/apache-log4j-1.2.15/log4j-1.2.15.jar -Dlog4j.configuration=log4j_console.properties -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=12122 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false org.apache.zookeeper.server.quorum.QuorumPeerMain zoo.cfg
> In addition to the ones in jira 234, we also need the following to connect remotely:
> -Dcom.sun.management.jmxremote.port
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false
> This command assumes no authentication or secure connection through ssl. To use authentication, other options are necessary, such as the password file:
> -Dcom.sun.management.jmxremote.password.file
> In general, I found the following page a good source of information on this topic:
> http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-274) Document options to connect
Jconsole remotely
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-274:
-----------------------------------
Component/s: jmx
> Document options to connect Jconsole remotely
> ---------------------------------------------
>
> Key: ZOOKEEPER-274
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-274
> Project: Zookeeper
> Issue Type: Improvement
> Components: jmx
> Reporter: Flavio Paiva Junqueira
> Priority: Minor
>
> Here is the command I used:
> java -cp .:./zookeeper-dev.jar:/usr/local/apache-log4j-1.2.15/log4j-1.2.15.jar -Dlog4j.configuration=log4j_console.properties -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=12122 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false org.apache.zookeeper.server.quorum.QuorumPeerMain zoo.cfg
> In addition to the ones in jira 234, we also need the following to connect remotely:
> -Dcom.sun.management.jmxremote.port
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false
> This command assumes no authentication or secure connection through ssl. To use authentication, other options are necessary, such as the password file:
> -Dcom.sun.management.jmxremote.password.file
> In general, I found the following page a good source of information on this topic:
> http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ZOOKEEPER-274) Document options to connect
Jconsole remotely
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt resolved ZOOKEEPER-274.
------------------------------------
Resolution: Invalid
Closing -- the ZK JMX documention (as of 3.1) includes details on this - in particular it includes
sun's agent configuration document, the same link detailed in this jira.
> Document options to connect Jconsole remotely
> ---------------------------------------------
>
> Key: ZOOKEEPER-274
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-274
> Project: Zookeeper
> Issue Type: Improvement
> Components: jmx
> Reporter: Flavio Paiva Junqueira
> Assignee: Patrick Hunt
> Priority: Minor
> Fix For: 3.2.0
>
>
> Here is the command I used:
> java -cp .:./zookeeper-dev.jar:/usr/local/apache-log4j-1.2.15/log4j-1.2.15.jar -Dlog4j.configuration=log4j_console.properties -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=12122 -Dcom.sun.management.jmxremote.local.only=false -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false org.apache.zookeeper.server.quorum.QuorumPeerMain zoo.cfg
> In addition to the ones in jira 234, we also need the following to connect remotely:
> -Dcom.sun.management.jmxremote.port
> -Dcom.sun.management.jmxremote.authenticate=false
> -Dcom.sun.management.jmxremote.ssl=false
> This command assumes no authentication or secure connection through ssl. To use authentication, other options are necessary, such as the password file:
> -Dcom.sun.management.jmxremote.password.file
> In general, I found the following page a good source of information on this topic:
> http://java.sun.com/javase/6/docs/technotes/guides/management/agent.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.