[CASSANDRA-6110] Workaround for JMX random port selection

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Duplicate
• Assignee: Unassigned
• Reporter: J.B. Langston
• Created: 29/Sep/13 20:39
• Updated: 16/Apr/19 09:32
• Resolved: 07/May/14 15:39

Description

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 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.

Issue Links

• is duplicated by: CASSANDRA-7087 Use JMX_PORT for the RMI port to simplify nodetool connectivity