You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2016/05/06 07:28:12 UTC
[jira] [Created] (CASSANDRA-11725) Check for unnecessary JMX port
setting in env vars at startup
Sam Tunnicliffe created CASSANDRA-11725:
-------------------------------------------
Summary: 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: Improvement
Components: Lifecycle
Reporter: Sam Tunnicliffe
Priority: Minor
Fix For: 3.x
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)