[
https://issues.apache.org/jira/browse/CASSANDRA-11725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-11725:
----------------------------------------
Assignee: Sam Tunnicliffe
Reviewer: T Jake Luciani
Status: Patch Available (was: Open)
I've pushed a branch which adds a {{StartupCheck}} that warns if
{{com.sun.management.jmxremote.port}} is set.
As this issue also exposed the fact that a number of clients where relying on
passing the JMX config directly via system properties, rather than using
{{cassandra-env.sh}}, I've made startup more permissive to emulate previous
behaviour. So, if the property is present, when it C* comes to init the JMX
server it will log an additional warning and skip the setup.
The additional warning is because at some point, we should remove this
compatibility mode and go back to failing startup if the {{jmxremote.port}} is
set directly, but we'll the {{StartupCheck}} should remain.
||branch||testall||dtest||
|[11725-3.6|https://github.com/beobal/cassandra/tree/11725-3.6]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-11725-3.6-testall]|[dtest|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-11725-3.6-dtest]|
> 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
> Assignee: Sam Tunnicliffe
> Priority: Minor
> Labels: lhf
> 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)
