cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6110) Workaround for JMX random port selection
Date Mon, 30 Sep 2013 15:54:24 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781951#comment-13781951
] 

Nick Bailey commented on CASSANDRA-6110:
----------------------------------------

We decided to leave this as an exercise for the user here CASSANDRA-2967. 

Not sure much has changed since then.

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

Mime
View raw message