[
https://issues.apache.org/jira/browse/CASSANDRA-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040372#comment-14040372
]
Chris Lohfink commented on CASSANDRA-7254:
------------------------------------------
My thoughts:
* remove rmi port option until jvm fixed
* 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
* custom java agent that would do kind of a "preflight check" on startup,
giving some appropriate warnings if any ports are used etc
* ignore it until fixed (not ideal, but complexity for fixes might be worse
then error)
any feedback on a good approach?
> 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)
