cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Agrawal, Pratik" <paagr...@amazon.com>
Subject Cassandra unit tests broke after upgrading from Cassandra 2.0.9 to Cassandra 2.2.4
Date Mon, 16 May 2016 21:13:08 GMT
Hello all,

In Cassandra 2.0.9 we used to unit test Cassandra Client side code by starting a local Cassandra
server through code. We used to do the following:

1.) Initialize Yaml file by providing YAML file path:
System.setProperty("cassandra.config", "file://" + TEMP_YAML_LOCATION);

2.) Initialize Cassandra daemon:
CassandraDaemon cassandraDaemon = new CassandraDaemon();
cassandraDaemon.init(null);

3.) Start Cassandra Server:
cassandraDaemon.start()

And the local Cassandra Server used to start fine, but after upgrading to Cassandra 2.2.4
whenever we try to run unit tests the JVM crashes at step 2, particularly at cassandraDaemon.init().
The error message is "A fatal error has been detected by the Java Runtime Environment"

#  SIGSEGV (0xb) at pc=0x00002b5bf0538ae7, pid=22912, tid=47673884399936
#
# JRE version: Java(TM) SE Runtime Environment (8.0_31-b13) (build 1.8.0_31-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.31-b07 mixed mode linux-amd64 compressed
oops)
# Problematic frame:
# V  [libjvm.so+0x6a1ae7]  jni_IsInstanceOf+0xb7

Did anything change in Cassandra 2.2? Any help in this regard would be appreciated.

Thanks,
Pratik



Mime
View raw message