[
https://issues.apache.org/jira/browse/CASSANDRA-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044103#comment-14044103
]
Tyler Hobbs commented on CASSANDRA-7254:
----------------------------------------
Damn, none of those options are very good.
bq. remove rmi port option until jvm fixed
Most users won't be on the latest and greatest JVM, and JMX port madness has
caused a lot of problems for users.
bq. write a java app (platform independent, would have to work in many
environments) that checks ports being open with appropariate and execute it in
the bat/sh scripts to give a better warning
This would need to use (parts of) the cassandra config and environment
variables. I guess it's doable, just a pain.
bq. custom java agent that would do kind of a "preflight check" on startup,
giving some appropriate warnings if any ports are used etc
We wouldn't have to set up a separate process for this, which is nice. My main
concern is implementing all of the JMX features correctly in a custom agent,
making sure it works across multiple java versions, and that future java
versions don't break it.
bq. ignore it until fixed (not ideal, but complexity for fixes might be worse
then error)
I guess Google will work reasonable well for users who hit this.
I also played around with piping stderr through a process that could look for
this particular string and output something more reasonable if found. It seems
like this would be pretty hard to make portable across shells, even if we
ignore windows. Somebody with more advanced shell-fu than I have might have a
good idea, though.
Did you go ahead and open a JVM ticket?
> NPE on startup if another Cassandra instance is already running
> ---------------------------------------------------------------
>
> Key: CASSANDRA-7254
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7254
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Tyler Hobbs
> Assignee: Chris Lohfink
> Priority: Minor
> Fix For: 2.1.0
>
>
> After CASSANDRA-7087, if you try to start cassandra while another instance is
> already running, you'll see something like this:
> {noformat}
> $ bin/cassandra -f
> Error: Exception thrown by the agent : java.lang.NullPointerException
> {noformat}
> This is probably a JVM bug, but we should confirm that, open a JVM ticket,
> and see if we can give a more useful error message on the C* side.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
