[ 
https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sam Tunnicliffe updated CASSANDRA-11695:
----------------------------------------
    Resolution:     (was: Fixed)
        Status: Open  (was: Resolved)

Looks like this breaks simulator tests, for example 
{{ShortPaxosSimulationTest}}:
{code}
hread[isolatedExecutor:2,5,node1]
org.apache.cassandra.exceptions.ConfigurationException: Invalid value for 
system property: expected integer value but got ''
        at 
org.apache.cassandra.config.CassandraRelevantProperties.lambda$static$1(CassandraRelevantProperties.java:988)
        at 
org.apache.cassandra.config.CassandraRelevantProperties.getInt(CassandraRelevantProperties.java:806)
        at 
org.apache.cassandra.config.JMXServerOptions.createParsingSystemProperties(JMXServerOptions.java:155)
        at 
org.apache.cassandra.config.DatabaseDescriptor.applySimpleConfig(DatabaseDescriptor.java:978)
        at 
org.apache.cassandra.config.DatabaseDescriptor.applyAll(DatabaseDescriptor.java:524)
        at 
org.apache.cassandra.config.DatabaseDescriptor.daemonInitialization(DatabaseDescriptor.java:281)
        at 
org.apache.cassandra.config.DatabaseDescriptor.daemonInitialization(DatabaseDescriptor.java:267)
        at 
org.apache.cassandra.distributed.impl.Instance.partialStartup(Instance.java:711)
        at 
org.apache.cassandra.distributed.impl.Instance.lambda$startup$7(Instance.java:634)
        at 
org.apache.cassandra.concurrent.FutureTask$2.call(FutureTask.java:124)
        at 
org.apache.cassandra.concurrent.SyncFutureTask.run(SyncFutureTask.java:68)
        at 
org.apache.cassandra.simulator.systems.InterceptingExecutor$InterceptingPooledExecutor$WaitingThread.lambda$new$1(InterceptingExecutor.java:318)
{code}

this is due to {{o.a.c.simulation.SimulationRunner}} which does:
{code}
        CASSANDRA_JMX_REMOTE_PORT.setString("");
{code}

I think it should be safe to just remove that and leave the remote port unset, 
but I'm not 100% clear on why it's set in the first place so would be best to 
check first.

> Move JMX connection config to cassandra.yaml
> --------------------------------------------
>
>                 Key: CASSANDRA-11695
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11695
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Local/Config
>            Reporter: Sam Tunnicliffe
>            Assignee: Stefan Miklosovic
>            Priority: Low
>              Labels: lhf
>             Fix For: 5.1
>
>          Time Spent: 6h 20m
>  Remaining Estimate: 0h
>
> Since CASSANDRA-10091, we always construct the JMX connector server 
> programatically, so we could move its configuration from cassandra-env to 
> yaml.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to