[
https://issues.apache.org/jira/browse/CASSANDRA-9089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp resolved CASSANDRA-9089.
-------------------------------------
Resolution: Won't Fix
After chatting with T Jake we agreed to not implement this.
Although I still like the idea to make the listen address configurable, doing
so would make RMI GC (OOM) issues reappear. I completely forgot that this ugly
beast exists.
As a workaround (actually a better solution), people should just configure
{{iptables}} correctly to restrict access to the JMX port.
> Make JMX listen address configurable
> ------------------------------------
>
> Key: CASSANDRA-9089
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9089
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Minor
>
> CASSANDRA-9085 introduced the ability to set the address the JMX server binds
> to. It's beneficial to have JMX listen to a specific address (default to the
> loopback address is fine).
> Any preferences whether to do that for 2.1 or 3.0?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
