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

Stefan Miklosovic updated CASSANDRA-18572:
------------------------------------------
    Description: 
Instance.nodetoolResult is not using JMX internally but it throws 
UnsupportedOperationException in InternalNodeProbe for some nodetool comamnds.

This makes calls to instance.nodetoolResult("info"), for example, impossible, 
because these commands are using JMX / calling methods which are throwing 
exception and it makes the testing painful.

There is no reason to not support this if Instance has JMX feature as it was 
added recently.

  was:
Instance.nodetoolResult is not using JMX internally but it throws 
UnsupportedOperationException in InternalNodeProbe.

This makes calls to instance.nodetoolResult("info"), for example, impossible, 
because these commands are using JMX / calling methods which are throwing 
exception and it makes the testing painful.

There is no reason to not support this if Instance has JMX feature as it was 
added recently.


> Instance.nodetoolResult should connect to JMX if there is such feature 
> enabled in its config
> --------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-18572
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18572
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Test/dtest/java
>            Reporter: Stefan Miklosovic
>            Assignee: Stefan Miklosovic
>            Priority: Normal
>             Fix For: 3.11.x, 4.0.x, 4.1.x, 5.x
>
>         Attachments: fix-jmx-issue-on-shutdown.patch
>
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> Instance.nodetoolResult is not using JMX internally but it throws 
> UnsupportedOperationException in InternalNodeProbe for some nodetool comamnds.
> This makes calls to instance.nodetoolResult("info"), for example, impossible, 
> because these commands are using JMX / calling methods which are throwing 
> exception and it makes the testing painful.
> There is no reason to not support this if Instance has JMX feature as it was 
> added recently.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to