[
https://issues.apache.org/jira/browse/CASSANDRA-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122521#comment-14122521
]
Chris McEniry commented on CASSANDRA-7254:
------------------------------------------
Katsutoshi Nagaoka This is more that jolokia causes the preflight java run that
was added in this issue to not exit and hangs up the startup script. The
jvm-not-existing behavior happens even if you just try to startup java with
only the -javaagent:jolokia.jar so I'm thinking it might be more for the
jolokia crew to decide if that's intended behavior or not.
Two thoughts on work around:
1.) (undo) You can out the preflight but then you'll see the NPEs that this was
trying to avoid
2.) Instead of running jolokia as a commandline javaagent, have it attach after
the start (http://www.jolokia.org/reference/html/agents.html#jvm-attach), but
then you'll have to update the service start script or do some other manual
start.
> 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: 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)
