You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "J.B. Langston (JIRA)" <ji...@apache.org> on 2013/09/29 22:39:23 UTC

[jira] [Created] (CASSANDRA-6110) Workaround for JMX random port selection

J.B. Langston created CASSANDRA-6110:
----------------------------------------

             Summary: Workaround for JMX random port selection
                 Key: CASSANDRA-6110
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6110
             Project: Cassandra
          Issue Type: Improvement
            Reporter: J.B. Langston
            Priority: Minor


Many people have been annoyed by the way that JMX selects a second port at random for the RMIServer, which makes it almost impossible to use JMX through a firewall.  There is a [workaround|https://blogs.oracle.com/jmxetc/entry/connecting_through_firewall_using_jmx] using a custom java agent.  Since jamm is already specified as the java agent for Cassandra, this would have to subclass or wrap the jamm MemoryMeter class.



--
This message was sent by Atlassian JIRA
(v6.1#6144)