cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Witschey (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10834) flapping when Jolokia fails to connect
Date Wed, 09 Dec 2015 17:23:11 GMT


Jim Witschey commented on CASSANDRA-10834:

My mistake, I didn't realize 10666 was closed so recently [~krummas], thanks for pointing
that out. Closing as a duplicate.

> flapping when Jolokia fails to connect
> -------------------------------------------------------------------------------
>                 Key: CASSANDRA-10834
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
> {{}} flaps in a number of jobs on CassCI, including
the 3.0 and trunk jobs:
> There may be other jobs and other tests that flap this way; I'll update this ticket as
appropriate if I find more information.
> The error printed by the test is
> {code}
> Failed to start jolokia agent (command was: /usr/lib/jvm/jdk1.8.0_45/bin/java -cp /usr/lib/jvm/jdk1.8.0_45/lib/tools.jar:lib/jolokia-jvm-1.2.3-agent.jar
org.jolokia.jvmagent.client.AgentLauncher --host start 17785): Command '('/usr/lib/jvm/jdk1.8.0_45/bin/java',
'-cp', '/usr/lib/jvm/jdk1.8.0_45/lib/tools.jar:lib/jolokia-jvm-1.2.3-agent.jar', 'org.jolokia.jvmagent.client.AgentLauncher',
'--host', '', 'start', '17785')' returned non-zero exit status 1
> Exit status was: 1
> Output was: Illegal Argument (command: start) : Cannot attach to process-ID 17785.
> See --help for possible reasons.
> {code}
> Which is not very helpful. However, that message is consistent with the one found in
the error that led to us filing this ticket:
> So, one starting point for debugging should should be to check that shared memory is
correctly disabled when launching Cassandra.
> This was originally reported as CASSANDRA-10666, but that got derailed when an OOM error
cropped up on the same test.

This message was sent by Atlassian JIRA

View raw message