You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yang Yang (JIRA)" <ji...@apache.org> on 2011/02/11 06:50:57 UTC
[jira] Created: (CASSANDRA-2153) client temporarily freezes due to
hard-coded JMX port
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
[jira] Reopened: (CASSANDRA-2153) client temporarily freezes due to
hard-coded JMX port
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis reopened CASSANDRA-2153:
---------------------------------------
Assignee: Pavel Yaskevich
Hmm, looks like we accept --jmxport as an option but it doesn't get passed to CliSessionState's NodeProbe
> 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
[jira] Commented: (CASSANDRA-2153) client temporarily freezes due
to hard-coded JMX port
Posted by "Yang Yang (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (CASSANDRA-2153) client temporarily freezes due to
hard-coded JMX port
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: 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
[jira] Updated: (CASSANDRA-2153) client temporarily freezes due to
hard-coded JMX port
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2153:
--------------------------------------
Fix Version/s: 0.7.2
> 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
[jira] Resolved: (CASSANDRA-2153) client temporarily freezes due to
hard-coded JMX port
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-2153.
---------------------------------------
Resolution: Not A Problem
use --jmxport
> 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
[jira] Commented: (CASSANDRA-2153) client temporarily freezes due
to hard-coded JMX port
Posted by "Pavel Yaskevich (JIRA)" <ji...@apache.org>.
[ 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