[
https://issues.apache.org/jira/browse/CASSANDRA-11725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280329#comment-15280329
]
Michael Shuler commented on CASSANDRA-11725:
--------------------------------------------
Confirming this commit works for allowing public IP setting in
{{java.rmi.server.hostname}} on a cloud server that does not know its public
IP. That bind was failing previously, but works out fine now. Thanks!
> Check for unnecessary JMX port setting in env vars at startup
> -------------------------------------------------------------
>
> Key: CASSANDRA-11725
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11725
> Project: Cassandra
> Issue Type: Bug
> Components: Lifecycle
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Minor
> Labels: lhf
> Fix For: 3.6
>
>
> Since CASSANDRA-10091, C* expects to always be in control of initializing its
> JMX connector server. However, if {{com.sun.management.jmxremote.port}} is
> set when the JVM is started, the bootstrap agent takes over and sets up the
> server before any C* code runs. Because C* is then unable to bind the server
> it creates to the specified port, startup is halted and the root cause is
> somewhat unclear.
> We should add a check at startup so a more informative message can be
> provided. This would test for the presence of the system property which would
> differentiate from the case where some other process is already bound to the
> port.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
