The problem still exists. There was a discussion about resolving inside cassandra here:
https://issues.apache.org/jira/browse/CASSANDRA-2967 But the ultimate resolution was that since workarounds like the one you mentioned exist it would be left as is for now. On Mon, Aug 27, 2012 at 6:07 PM, Yang <teddyyyy...@gmail.com> wrote: > no, the priblem is that jmx listens on 7199, once an incoming connection is > made, it literally tells the other side "come and connect to me on these 2 > rmi ports", and open up 2 random Rmi ports > > we used to use the trick in the above link to resolve this > > On Aug 27, 2012 3:04 PM, "Hiller, Dean" <dean.hil...@nrel.gov> wrote: >> >> In cassandra-env.sh, search on JMX_PORT and it is set to 7199 (ie. Fixed) >> so that solves your issue, correct? >> >> Dean >> >> From: Yang <teddyyyy...@gmail.com<mailto:teddyyyy...@gmail.com>> >> Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" >> <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> >> Date: Monday, August 27, 2012 3:44 PM >> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" >> <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> >> Subject: JMX(RMI) dynamic port allocation problem still exists? >> >> ow, does Cassandra come with an out-of-the box solution to fix the above >> problem? or do I have >> to create that little javaagent jar myself?
