[
https://issues.apache.org/jira/browse/CASSANDRA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993850#comment-12993850
]
Yang Yang commented on CASSANDRA-2153:
--------------------------------------
if it were to be left as it is, it would also be helpful to put a comment there
saying "these will be directed modified". I was kind of expecting
setters/getters style
> client temporarily freezes due to hard-coded JMX port
> -----------------------------------------------------
>
> Key: CASSANDRA-2153
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2153
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.0
> Reporter: Yang Yang
>
> when you do a "show keyspaces" inside cassandra-cli,
> on the current 0.7 head svn,
> the client CliSessionState.java hardcodes the JMX port to be 8080
> so if there is indeed a webserver listening on 8080, it gets the connection
> and indeed tries to talk to it, but the protocol doesn't make sense to
> cassandra-cli , so it freezes for about 10 seconds before finally giving up.
> changing the hardcoded value to my actual jmx port fixes the issue.
> so this should be read from config file or argument
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
