cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Resolved: (CASSANDRA-2153) client temporarily freezes due to hard-coded JMX port
Date Fri, 11 Feb 2011 15:00:59 GMT


Jonathan Ellis resolved CASSANDRA-2153.

       Resolution: Not A Problem
    Fix Version/s:     (was: 0.7.2)
         Assignee:     (was: Pavel Yaskevich)

I'd rather create the SessionState object with the correct, final values, than rely on mutating
them later, but it does work functionally.

> client temporarily freezes due to hard-coded JMX port
> -----------------------------------------------------
>                 Key: CASSANDRA-2153
>                 URL:
>             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 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:


View raw message