[
https://issues.apache.org/jira/browse/CASSANDRA-10834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049001#comment-15049001
]
Jim Witschey commented on CASSANDRA-10834:
------------------------------------------
Ah, I missed something. Looks like this is related to an OOM that's happening
during the test:
http://cassci.datastax.com/job/trunk_dtest/820/testReport/junit/jmx_test/TestJMX/test_compactionstats_2/
I haven't debugged to see if there's a causal relationship in one direction or
the other, but perhaps the resolution to CASSANDRA-10666 didn't fix the OOM.
> jmx_test.py:TestJMX.test_compactionstats flapping when Jolokia fails to
> connect
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-10834
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10834
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jim Witschey
>
> {{jmx_test.py:TestJMX.test_compactionstats}} flaps in a number of jobs on
> CassCI, including the 3.0 and trunk jobs:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/335/testReport/junit/jmx_test/TestJMX/test_compactionstats/history/
> http://cassci.datastax.com/job/trunk_dtest/820/testReport/jmx_test/TestJMX/test_compactionstats/history/
> 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 127.0.0.1 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', '127.0.0.1', '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:
> https://github.com/rhuss/jolokia/issues/198
> 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
(v6.3.4#6332)
