[
https://issues.apache.org/jira/browse/CASSANDRA-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668175#comment-15668175
]
Shannon Carey commented on CASSANDRA-7254:
------------------------------------------
Thanks. As it turns out, I think I had a similar issue as Jolokia where a rogue
JVM agent created a non-daemon thread which prevented JVM termination despite
presence of a JVM shutdown hook (those don't execute until all non-daemon
threads have stopped). My initial theory regarding port usage seems to have
been incorrect.
> 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
> Reporter: Tyler Hobbs
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 2.0.10, 2.1 rc3
>
> Attachments: 7254.txt
>
>
> 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.3.4#6332)
