Differences between revisions 1 and 2
Revision 1 as of 2010-04-05 22:27:23
Size: 771
Editor: EricEvans
Comment: misplaced material excised from RunningCassandra
Revision 2 as of 2011-05-12 18:40:55
Size: 931
Editor: c-76-126-67-196
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
 * If you run into issues connecting via jconsole to the JmxInterface port from a remote machine, it may be the JVM option '-Djava.rmi.server.hostname'. This may need to be set to a particular interface like '-Djava.rmi.server.hostname=$IP' (where $IP is the ip address of the interface you can reach from the remote machine). Java defaults to the ip address of "localhost" which is mostly likely not what you want.
 * You may also run into issues connecting to the JMX interface (even locally) because by default JMX binds to IPv6 if it's available (netstat -nap | grep 8080). This case is also solved by passing '-Djava.rmi.server.hostname=$IP' explicitly as a JVM option. This will prompt JMX to bind to the given IPv4 IP address so that nodetool can access it.
 * If you run into issues connecting via jconsole to the JmxInterface port from a remote machine, it may be the JVM is binded on a difference interface. To bind to a specific interface, you could use JVM option '-Djava.rmi.server.hostname=$IP' (where $IP is the ip address of the interface you want to reach from the remote machine). By default, the RMI implementation uses the server's IP address as indicated by the java.net.InetAddress.getLocalHost API.
 * You may also run into issues connecting to the JMX interface (even locally) because by default JMX binds to IPv6 if it's available. This case is also solved by passing '-Djava.net.preferIPv4Stack=true' explicitly as a JVM option. This will prompt JMX to bind to the given IPv4 IP address so that nodetool can access it.
 * To check the listening interface, whether it is on the correct host name or IPv4/IPv6, the following command could be used: '''netstat -ltn'''
  • If you run into issues connecting via jconsole to the JmxInterface port from a remote machine, it may be the JVM is binded on a difference interface. To bind to a specific interface, you could use JVM option '-Djava.rmi.server.hostname=$IP' (where $IP is the ip address of the interface you want to reach from the remote machine). By default, the RMI implementation uses the server's IP address as indicated by the java.net.InetAddress.getLocalHost API.

  • You may also run into issues connecting to the JMX interface (even locally) because by default JMX binds to IPv6 if it's available. This case is also solved by passing '-Djava.net.preferIPv4Stack=true' explicitly as a JVM option. This will prompt JMX to bind to the given IPv4 IP address so that nodetool can access it.
  • To check the listening interface, whether it is on the correct host name or IPv4/IPv6, the following command could be used: netstat -ltn

JmxGotchas (last edited 2013-11-14 21:49:56 by 107)