Re: nodetool hangs

2014-04-24 Thread Chris Lohfink
Wow… wheres this been all my life. I don’t see why this can’t be set by default? https://issues.apache.org/jira/browse/CASSANDRA-7087 --- Chris Lohfink On Apr 24, 2014, at 11:48 AM, Steven A Robenalt wrote: > There's a little-known change in the way JMX uses ports that was add to > JDK7u4 w

Re: nodetool hangs

2014-04-24 Thread Steven A Robenalt
There's a little-known change in the way JMX uses ports that was add to JDK7u4 which simplifies the use of JMX in a firewalled environment. The standard RMI registry port for JMX is controlled by the com.sun.management.jmxremote.port property. The change to Java 7 was to introduce the related com.

Re: nodetool hangs

2014-04-24 Thread Chris Lohfink
The way RMI (which JMX uses, which is what nodetool uses) works is it will first connect, then send a address/port back over the wire for it to make a new 2nd connection too. This will be potentially to a different address then 127.0.0.1 (can override with -Djava.rmi.server.hostname= in /etc/c

Re: nodetool hangs and didn't print anything with firewall

2012-02-08 Thread Maxim Potekhin
That's good to hear because it does present a problem for a strictly manages and firewalled campus environment. Maxim On 2/6/2012 11:57 AM, Nick Bailey wrote: JMX is not very firewall friendly. The problem is that JMX is a two connection process. The first connection happens on port 7199 and t

Re: nodetool hangs and didn't print anything with firewall

2012-02-06 Thread Nick Bailey
JMX is not very firewall friendly. The problem is that JMX is a two connection process. The first connection happens on port 7199 and the second connection happens on some random port > 1024. Work on changing this behavior was started in this ticket: https://issues.apache.org/jira/browse/CASSANDRA

Re: nodetool hangs and didn't print anything with firewall

2012-02-06 Thread R. Verlangen
Do you allow both outbound as inbound traffic? You might also try allowing both TCP as UDP. 2012/2/6 Roshan > Yes, If the firewall is disable it works. > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/nodetool-hangs-and-didn-t-print-anythi

Re: nodetool hangs and didn't print anything with firewall

2012-02-05 Thread Mohit Anchlia
Does it work with iptables disabled? You could add log to your firewall rules to see if firewall is dropping the packets. On Sun, Feb 5, 2012 at 5:35 PM, Roshan wrote: > Hi > > I have 2 node Cassandra cluster and each linux box configured with a > firewall. The ports 7000, 7199 and 9160 are open