cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2153) client temporarily freezes due to hard-coded JMX port
Date Fri, 11 Feb 2011 14:54:57 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993522#comment-12993522
] 

Pavel Yaskevich commented on CASSANDRA-2153:
--------------------------------------------

Re-tested on both cassandra-0.7 and trunk - works fine, you can see CliOptions.java:157 (place
where JMX port from arguments gets passed to the CliSessionState)

> 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
>            Assignee: Pavel Yaskevich
>             Fix For: 0.7.2
>
>
> 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

        

Mime
View raw message