cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-7087) Use JMX_PORT for the RMI port to simplify nodetool connectivity
Date Thu, 24 Apr 2014 19:55:15 GMT


Brandon Williams updated CASSANDRA-7087:

         Reviewer: Brandon Williams
    Fix Version/s: 2.1 beta2
         Assignee: Chris Lohfink

Nice!  Committed this to 2.0 and above so we don't have to fool with jvm version detection
(even though we already have the code to do that.)

> Use JMX_PORT for the RMI port to simplify nodetool connectivity
> ---------------------------------------------------------------
>                 Key: CASSANDRA-7087
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Config
>            Reporter: Chris Lohfink
>            Assignee: Chris Lohfink
>            Priority: Minor
>              Labels: security
>             Fix For: 2.0.8, 2.1 beta2
>         Attachments: patch.txt
> Mentioned in the user list by Steven Robenalt there is a config option in Java7 to allow
configuring the port used for the followup rmi connection in JMX.  It simplifies things a
lot to have both connections use 7199 since it could be reused for both.
> bq. 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 property. The change to Java 7
was to introduce the related property, Setting this
second property means that JMX will use that second port, rather than a randomly assigned
port, for making the actual connection. This solution works well in the AWS VPC environment
that I'm running in, and I've heard of others using it successfully as well.

This message was sent by Atlassian JIRA

View raw message