cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1946) cassandra-cli always uses port 8080 (show keyspaces brings up a WARNing), no matter which port is defined in cassandra-env.sh
Date Fri, 07 Jan 2011 08:07:46 GMT

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

Jonathan Ellis updated CASSANDRA-1946:
--------------------------------------

    Fix Version/s: 0.7.1
         Assignee: Pavel Yaskevich

> cassandra-cli always uses port 8080 (show keyspaces brings up a WARNing), no matter which
port is defined in cassandra-env.sh
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-1946
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1946
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 0.7.0
>         Environment: Ubuntu 10.10, JDK 1.6.0_23
>            Reporter: Markus Wiesenbacher
>            Assignee: Pavel Yaskevich
>            Priority: Trivial
>             Fix For: 0.7.1
>
>
> In cassandra-cli I do a "show keyspaces;", this bring up this WARNing:
> WARNING: Could not connect to the JMX on 10.1.1.106:8080, information won't be shown.
> JMX (mx4j-tools) is up and running, but on port 18080 (defined in cassandra-env.sh),
so the problem should be that the CLI uses 8080 statically?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message