You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Markus Wiesenbacher (JIRA)" <ji...@apache.org> on 2011/01/07 07:57:46 UTC
[jira] Created: (CASSANDRA-1946) cassandra-cli always uses port
8080 (show keyspaces brings up a WARNing), no matter which port is defined
in cassandra-env.sh
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
Priority: Trivial
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.
[jira] Commented: (CASSANDRA-1946) cassandra-cli always uses port
8080 (show keyspaces brings up a WARNing), no matter which port is defined
in cassandra-env.sh
Posted by "Pavel Yaskevich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978725#action_12978725 ]
Pavel Yaskevich commented on CASSANDRA-1946:
--------------------------------------------
I have added --jmxport <port> option to the cli to specify JMX port, can you please try to use it?
> 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.
[jira] Closed: (CASSANDRA-1946) cassandra-cli always uses port 8080
(show keyspaces brings up a WARNing), no matter which port is defined in
cassandra-env.sh
Posted by "Markus Wiesenbacher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Markus Wiesenbacher closed CASSANDRA-1946.
------------------------------------------
Works fine, many thanks! ;)
> 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
>
> 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.
[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
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (CASSANDRA-1946) cassandra-cli always uses port
8080 (show keyspaces brings up a WARNing), no matter which port is defined
in cassandra-env.sh
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-1946.
---------------------------------------
Resolution: Not A Problem
Fix Version/s: (was: 0.7.1)
> 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
>
> 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.